Systems and methods to process payments via account identifiers and phone numbers

ABSTRACT

Systems and methods are provided to facilitate transactions via mobile communications. In one aspect, a system includes a data storage facility and an interchange coupled with the data storage facility that stores data associating a phone number of a user and an account identifier of the user. The interchange includes a common format processor and a plurality of converters to interface with a plurality of different controllers of mobile communications. The converters are configured to communicate with the controllers in different formats and with the common format processor in a common format. The common format processor uses one of the converters to transmit premium messages to the phone number to collect funds via a telecommunication carrier, receives a payment request having the account identifier, identifies the phone number based on the account identifier, and makes a payment on behalf of the user using the collected funds.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of Prov. U.S. Pat. App. Ser.No. 61/428,202, filed Dec. 29, 2010 and entitled “Systems and Methods toProcess Payments via Account Identifiers and Phone Numbers,” thedisclosure of which is hereby incorporated herein by reference.

FIELD OF THE TECHNOLOGY

At least some embodiments of the disclosure relate to mobilecommunications in general and, more particularly but not limited to,mobile communications to facilitate online transactions.

BACKGROUND

Short Message Service (SMS) is a communications protocol that allows theinterchange of short text messages between mobile telephone devices. SMSmessages are typically sent via a Short Message Service Center (SMSC) ofa mobile carrier, which uses a store-and-forward mechanism to deliverthe messages. When a mobile telephone is not reachable immediately forthe delivery of the message, the SMSC stores the message for laterretry.

SMS messages can be sent via gateways. Some gateways function asaggregators. An aggregator typically does not have the capacity todeliver the messages directly to the mobile phones. An aggregatortypically interfaces with and relies upon the SMSC of a mobile carrierto deliver SMS messages.

Some gateways function as providers that are capable of sending textmessages to mobile devices directly, without going through the SMSC ofother mobile operators.

Text messaging between mobile telephones can also be performed usingother protocols, such as SkyMail and Short Mail in Japan.

Some mobile carriers provide email gateway services to allow textmessages to be sent to mobile phones via email. For example, anon-subscriber of the mobile carrier may send a message to an emailaddress associated with a mobile phone of a subscriber of the mobilecarrier to have the message delivered to the mobile phone via textmessaging.

Emails can also be sent to mobile telephone devices via standard mailprotocols, such as Simple Mail Transfer Protocol (SMTP) over InternetProtocol Suite (commonly TCP/IP, named from two of the protocols: theTransmission Control Protocol (TCP) and the Internet Protocol (IP)).

Short messages may be used to provide premium services to mobile phones,such as news alerts, ring tones, etc. The premium content providers maysend the messages to the SMSC of the mobile operator using a TCP/IPprotocol, such as Short Message Peer-to-peer Protocol (SMPP) orHypertext Transfer Protocol, for delivery to a mobile phone; and themobile phone is billed by the mobile operator for the cost of receivingthe premium content.

Premium services may also be delivered via text messages initiated fromthe mobile phone. For example, a televoting service provider may obtaina short code to receive text messages from mobile phones; and when theuser sends a text message to the short code, the mobile carrier routesthe message to the televoting service provider and charges the user afee, a portion of which is collected for the televoting serviceprovider.

SUMMARY OF THE DESCRIPTION

Systems and methods are provided to facilitate transactions via mobilecommunications. Some embodiments are summarized in this section.

In one aspect, a system includes a data storage facility to store dataassociating a phone number of a user and an account identifier of theuser, and an interchange coupled with the data storage facility. In oneembodiment, the interchange includes a common format processor and aplurality of converters to interface with a plurality of differentcontrollers of mobile communications. The converters are configured tocommunicate with the controllers in different formats; and theconverters are configured to communicate with the common formatprocessor in a common format.

In one embodiment, the common format processor is configured to use oneconverter of the converters to transmit premium messages to the phonenumber to collect funds via a telecommunication carrier of the phonenumber, receive a payment request having the account identifier and usethe account data to identify the phone number based on the accountidentifier in the payment request, and make a payment on behalf of theuser using the funds collected via the telecommunication carrier.

In another aspect, a method includes: receiving, in a computingapparatus, a payment request, the payment request identifying an accountidentification number issued by a bank to a user, the accountidentification number representing an account of the user at the bank;determining, using the computing apparatus, a phone number associatedwith the account identification number; and processing, by the computingapparatus, the payment request using a funding source associated withthe phone number, the funding source being different from the account atthe bank identified by the account identification number.

The disclosure includes methods and apparatuses which perform thesemethods, including data processing systems which perform these methods,and computer readable media containing instructions which when executedon data processing systems cause the systems to perform these methods.

Other features will be apparent from the accompanying drawings and fromthe detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which like referencesindicate similar elements.

FIG. 1 shows a system to facilitate online transactions according to oneembodiment.

FIG. 2 shows an interchange to route messages according to oneembodiment.

FIG. 3 shows a message processor according to one embodiment.

FIG. 4 shows a method to facilitate an online transaction using aninterchange according to one embodiment.

FIG. 5 illustrates a user interface to associate an account with atelephone number according to one embodiment.

FIG. 6 illustrates another user interface to associate an account with atelephone number according to one embodiment.

FIG. 7 illustrates a user interface to initiate a payment transactionaccording to one embodiment.

FIG. 8 illustrates a user interface to initiate a payment requestaccording to one embodiment.

FIG. 9 illustrates a user interface to confirm a payment requestaccording to one embodiment.

FIG. 10 illustrates a user interface to confirm the completion of apayment transaction according to one embodiment.

FIG. 11 illustrates a way to redirect a payment confirmation accordingto one embodiment.

FIG. 12 illustrates a user interface to receive payment optionsaccording to one embodiment.

FIG. 13 shows a method to process an online payment according to oneembodiment.

FIG. 14 shows another method to facilitate a payment transactionaccording to one embodiment.

FIG. 15 illustrates a user interface to confirm a transaction accordingto one embodiment.

FIG. 16 illustrates a mobile phone configured to confirm transactionsaccording to one embodiment.

FIGS. 17-19 illustrate methods to confirm transactions according to oneembodiment.

FIG. 20 shows a user interface to sign a user in according to oneembodiment.

FIG. 21 shows a user interface to obtain a phone number to sign a userin according to one embodiment.

FIG. 22 shows a mobile user interface to confirm the identity of a useraccording to one embodiment.

FIG. 23 shows another user interface to sign a user in according to oneembodiment.

FIG. 24 shows a system to sign a user in according to one embodiment.

FIG. 25 shows a method to sign a user in according to one embodiment.

FIGS. 26-29 show methods to approve a payment transaction according tosome embodiments.

FIGS. 30-33 show systems to facilitate retail transactions according tosome embodiments.

FIG. 34 shows a user interface to pre-approve a transaction according toone embodiment.

FIG. 35 shows a user interface to confirm an automatic teller machine(ATM) transaction according to one embodiment.

FIG. 36 shows a method performed on a retail terminal according to oneembodiment.

FIG. 37 shows a method to facilitate a retail transaction according toone embodiment.

FIG. 38 shows an account according to one embodiment.

FIG. 39 shows a method to make payments to one embodiment.

FIGS. 40-42 illustrate systems to make mobile phone based payments usingaccount identifiers according to some embodiments.

FIG. 43 shows a method to make payments via account identifiersaccording to one embodiment.

FIG. 44 shows a data processing system, which can be used in variousembodiments.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding. However, in certain instances, wellknown or conventional details are not described in order to avoidobscuring the description. References to one or an embodiment in thepresent disclosure are not necessarily references to the sameembodiment; and, such references mean at least one.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

In one embodiment, an interchange is used to interface with a pluralityof different controllers of mobile communications, such as SMS messages.The interchange can be used to associate account information with phonenumbers to facilitate electronic payments via mobile devices, such ascellular phones. The interchange is configured to communicate with themobile phones through the different controllers to provide security andconvenience for online transactions.

FIG. 1 shows a system to facilitate online transactions according to oneembodiment. In FIG. 1, an interchange (101) is provided to interfacewith a plurality of different controllers (115) for communications withthe mobile phones (117) over the wireless telecommunications network(105).

In FIG. 1, a data storage facility (107) stores user account information(121) and the corresponding phone numbers (123) of the mobile phones(117). The interchange (101) is coupled with the data storage facility(107) to communicate with the mobile phones (117) at the correspondingphone numbers (123) to confirm operations that are performed using theaccount information (121). Since the account information (121) issecured by the interchange (101), the account information (121) can beused to pay for products and services offered by the servers (113) ofvarious merchants, without being revealed to the merchants.

In one embodiment, the server (113) offers products and/or servicesadapted for a virtual world environment, such as an online gameenvironment, a virtual reality environment, etc. The products may bevirtual goods, which can be delivered via the transmission of data orinformation (without having to physically deliver an object to theuser). For example, the virtual goods may be a song, a piece of music, avideo clip, an article, a computer program, a decorative item for anavatar, a piece of virtual land in a virtual world, a virtual object ina virtual reality world, etc. For example, an online game environmenthosted on a server (113) may sell services and products via points orvirtual currency, which may be consumed by the user while engaging in agame session. For example, a virtual reality world hosted on a server(113) may have a virtual currency, which may be used by the residents ofthe virtual reality world to conduct virtual commerce within the virtualreality world (e.g., buy virtual lands, virtual stocks, virtual objects,services provided in the virtual reality world, etc). In otherembodiments, the server (113) may also offer physical goods, such asbooks, compact discs, photo prints, postcards, etc.

In FIG. 1, the interchange (101) may communicate with differentcontrollers (115) of mobile communications via different networks (e.g.,105 and 103) and/or protocols. The interchange (101) processes therequests in a common format and uses a set of converters forcommunications with the different controllers (115) respectively.

For example, the controllers (115) may be different aggregators,providers and/or SMSCs of different mobile carriers. Based on the phonenumbers (123), the interchange (101) interfaces with the correspondingcontrollers (115) to communicate with the mobile phones (117) via textmessaging to confirm the operations related to the corresponding accountinformation (121), such as bank accounts, credit card numbers, chargecard numbers, etc.

In FIG. 1, the user terminals (111) may use a unified interface to sendrequests to the interchange (101). For example, a website of theinterchange (101) may be used to receive the account information (121)from the web browsers running in the user terminals (111). The userterminals (111) are typically different from the mobile phones (117).However, in some embodiments, users may use the mobile phone (117) toaccess the web and submit the account information (121). Alternatively,the users may use the mobile phone (117) to submit the accountinformation (121) to the interchange (101) via text messaging, email,instant messaging, etc.

The use of the mobile phones (117) in the confirmation of activitiesthat involve the account information (121) increases the security of thetransaction, since the mobile phones (117) are typically secured in thepossession of the users.

Further, in one embodiment, the interchange (101) may use the phonebills of the mobile phones (117) to pay for purchases, in order to usethe account information (121) to pay for the phone bills, and/or todeposit funds into the accounts identified by the account information(121) by charging on the phone bills of the corresponding mobile phones(117). In some embodiments, the accounts identified by the accountinformation (121) are hosted on the data storage facility (107). Inother embodiments, the accounts are hosted on the account servers (125)of financial institutions, such as banks, credit unions, credit cardcompanies, etc.

In one embodiment, once the account information (121) is associated withthe mobile phones (117) via their phone numbers (123) stored in the datastorage facility (107), the users may use the user terminals (111) toaccess online servers (113) of various merchants or service providers tomake purchases. From the user terminals (111), the users can use theaccounts identified by the account information (121) to make the paymentfor the purchases, without revealing their account information (121) tothe operators of the servers (113).

In one embodiment, the mobile phones (117) are used by the correspondingusers to make payments and/or manage funds, such as for making purchasesin various websites hosted on the servers (113) of merchants and serviceproviders and/or for transferring funds to or from an account identifiedby the account information (121), such as phone bills of land-linetelephone services, credit card accounts, debit card accounts, bankaccounts, etc., or an account hosted on the data storage facility (107)or telecommunication accounts of the mobile phones (117) withtelecommunication carriers. The mobile phones (117) are used to confirmand/or approve the transactions associated with the account identifiedby the account information (121) (or other accounts). The interchange(101) interfaces the mobile phones (117) and the servers (113) toconfirm and/or approve transactions and to operate on the accountidentified by the account information (121) (and/or other accountsassociated with the phone number (123)).

For example, the user terminal (111) may provide the phone numbers (123)to the servers (113) to allow the servers (113) to charge the accountidentified by the account information (121) associated with the phonenumber (123). The interchange (101) sends a message to the mobile phone(117) via the phone number (123) to confirm the payment request. Oncethe payment is confirmed or approved via the corresponding mobile phone(117), the interchange (101) charges the account identified by theaccount information (121) (e.g., by communicating with the accountserver (125) on which the corresponding accounts are hosted) and paysthe server (113) on behalf of the user, using the funds obtained fromthe corresponding account identified by the account information (121).

In one embodiment, the user terminal (111) may not even provide thephone number (123) to the server (113) to process the payment. Theserver (113) may redirect a payment request to the interchange (101),which then prompts the user terminal (111) to provide the phone number(123) to the website of the interchange (101) to continue the paymentprocess.

For example, the server (113) may redirect the payment request to thewebsite of the interchange (101) with a reference indicating thepurchase made via the user terminal (111). The interchange (101) can usethe reference to subsequently complete the payment with the server (113)for the purchase, after receiving the phone number (123) directly fromthe user terminal (111) to confirm the payment via the mobile phone(117).

In some embodiments, instead of directly providing the phone number(123) to identify the account information (121), the user may provideother information to identify the phone number (123), such as an accountidentifier of the user assigned to the user for obtaining the servicesof the interchange (101).

In one embodiment, the account information (121) is pre-associated withthe phone number (123) prior to the payment request. The accountinformation (121) may be submitted to the interchange (101) via the userterminal (111) or the mobile phone (117) via a secure connection.

Alternatively, the user may supply the account information (121) to theinterchange (101) at the time the payment request is submitted from theuser terminal (111) to the interchange (101). Alternatively, the usermay supply the account information (121) to the interchange (101) at thetime the user responds to the confirmation message for the paymentrequest.

In some embodiments, the user may supply the account information (121)after a transaction using funds collected via the telecommunicationcarrier of the mobile phone (117) at the phone number (123). Forexample, after the transaction, the interchange (101) may send aninvitation message, such as a text message to the mobile phone (117) atthe phone number (123), to the user to invite the user to register withthe interchange (101) and provide the account information (121). Theuser may register with the interchange (101) via the mobile phone (117)(e.g., by a replying text message), or via a web page of the interchange(101) (e.g., using a link and/or a unique code provided in theinvitation message).

After the user registers with the interchange (101) (e.g., via themobile phone (117) and by providing the account information (121)), theuser may create a customized personal identification number (PIN) orreceive a PIN for enhanced security. Using the PIN, the user may use theaccount information (121) to complete an online transaction withouthaving to confirm and/or approve a transaction using the mobile phone(117). In some embodiments, the PIN may be used to reduce unwantedmessages to the mobile phone (117). For example, once the phone number(123) and the account information (121) are associated with a PIN, theinterchange (101) may require the user of the user terminal (111) toprovide the correct PIN to initiate the payment process. Thus, a spammerhaving only the phone number (123) (or a different user mistakenly usingthe phone number (123)) may not successfully use the user terminal (111)to request the interchange (101) to send confirmation messages to themobile phone (117) protected by the PIN. In some embodiments, theinterchange (101) may offer further incentives to the user forregistering with the interchange (101), such as reduced fees, discounts,coupons, free products and services, etc.

In one embodiment, once the account information (121) is associated withthe phone number (123) in the data storage facility (107), the user doesnot have to resubmit the account information (121) in subsequent paymentrequests.

By delegating the payment task to the interchange (101) and securing theaccount information (121) in the data storage facility (107), the systemas shown in FIG. 1 can increase the security of using the accountinformation (121) in an online environment.

In some embodiments, the interchange (101) can also fulfill the paymentrequests using the funds collected via the phone bill of the phonenumbers (123). The interchange (101) can collect the funds via sendingpremium messages to the mobile phones (117) at the phone numbers (123),after receiving confirmation from the mobile phone (117).

For example, after the confirmation or approval message is received fromthe mobile phone (117), the interchange (101) performs operations tocollect funds via the phone bill of the phone number (123). Theinterchange (101) may calculate the required premium messages to bill tothe mobile phone (117). For example, mobile terminated premium SMSmessages may have a predetermined set of prices for premium messages.The interchange (101) determines a combination of the premium messagesthat has a price closest to the amount required by the transaction, andsends this combination of premium messages to the mobile phone (117).For example, mobile originated premium SMS messages may also have apredetermined set of prices for premium messages. The interchange (101)can calculate the set of messages required for the transaction andtransmit a text message to the mobile phone (117) of the user toinstruct the user to send the required number of premium messages toprovide the funds.

FIG. 2 shows an interchange to route messages according to oneembodiment. In FIG. 2, the interchange (101) includes a unified datainterface (135) for interaction with the servers (113). The servers(113) may redirect the payment requests to the interchange (101) toallow the interchange (101) to subsequently communicate with the user toprocess the payment request, including obtaining payment options andidentifying user accounts (123), before returning to communicating withthe server (113). Alternatively, the servers (113) may collect accountrelated information (e.g., the phone number of the user) to requestpayment from the interchange (101).

In FIG. 2, the interchange (101) includes a common format processor(133), which processes various payment options in a common format. Inone embodiment, the common format processor (133) can handle thepayments via mobile terminated text message, mobile originated textmessage, operator bill, credit card, stored value account, and otheronline payment options. The common format processor (133) determines theactual amount that is to be billed to the user, based on the paymentoptions (e.g., mobile terminated premium SMS, mobile originated premiumSMS, operator billing, credit cards, etc.), and selects a converter(131) to communicate with a corresponding controller (115).

Different converters (131) are configured to communicate withcorresponding controllers (115) in different languages and protocols.The converters (131) perform the translation between the common formatused by the common format processor (133) and the corresponding formatsused by the controllers (115).

The use of the common format processor (133) simplifies the structure ofthe interchange (101) and reduces the development effort required forthe interchange (101) to interface with the increasing number ofdifferent controllers, such as SMSC, mobile providers, aggregators,gateways, etc.

FIG. 3 shows a message processor according to one embodiment. In FIG. 3,the common format processor (133) includes a billing engine (157) thatcalculates the amount to be billed to the user, by adding or subtractingtransaction costs for different billing methods, such as mobileterminated text message, mobile originated text message, operatorbilling, credit card, stored value account, and other online paymentoptions.

In one premium message billing method, the interchange (101) sendsmobile terminated premium SMS messages to the mobile phone (117) to billthe user, or requests the mobile phone (117) to send mobile originatedpremium SMS messages to a short code representing the interchange (101).

In one operator billing method, the interchange (101) directly sends amessage to the mobile carrier of the mobile phone (117) to bill theamount on the phone bill of the mobile phone (117), without having tosend a premium message to the mobile phone (117).

The common format processor (133) includes a decision engine (151) whichdecides how to generate a set of one or more messages to the mobilephone (117) based on a set of rules (141), regulations (143), limits(145), records (147) and restrictions (149).

For example, different countries have different regulations (143)governing the mobile communications with the mobile phones (117). Forexample, different mobile carriers have different rules (141) regardingpremium messages. For example, past transaction records (147) can beused to monitor the transactions to discover suspected fraudulentactivities. For example, parental limits (145) and merchant restrictions(149) can be imposed.

Based on results of the decision engine (151), the mobile messagegenerator (153) generates one or more messages to communicate with themobile phone (117) about the transaction (e.g., a request to collectfunds via the phone bill of the user for a payment request, or fordeposit into an account identified by the account information (121)).The converter (131) then interfaces with the corresponding controller(115) to transmit the messages to the mobile phones (117).

FIG. 4 shows a method to facilitate an online transaction using aninterchange according to one embodiment. In FIG. 4, the user terminal(111) provides (171) account information (121) to the interchange (101)for association with the phone number (123). For example, the user mayuse a device running a web browser as the user terminal (111) to submitthe account information (121) via a secure web connection. The userterminal (111) is typically different from the mobile phone (117).However, in some embodiments, the mobile phone (117) may also be used asthe user terminal (111) to submit the account information (121) (e.g.,via a wireless application protocol (WAP) application, or via a messagesent via short message service (SMS) or multimedia message service(MMS), or via an email message or an instant message).

After the user provides the account information (121) to the interchange(101) for storage in the data storage facility (107), the user can send(177) a charge request to the server (113) of a merchant from the userterminal (111). The server (113) of the merchant can send or redirect(179) the charge request to the interchange (101). In response to thecharge request, the interchange (101) sends (173) a confirmation messageto the mobile phone (117). If the user sends (173) an approval, or anappropriate reply, to the confirmation message from the mobile phone(117), the interchange (101) communicates with the account server (125)to charge an account of the user identified by the account information(121), without revealing the account information (121) to the server(113). The interchange (101) pays the merchant on behalf of the userusing the funds collected via charging the account of the user. Forexample, the interchange (101) may use its own bank account to pay themerchant operating the server (113). Thus, the financial information ofthe user is not revealed to the merchant.

Upon the completion of the payment process, the interchange (101) cannotify the user via the mobile phone (117) and/or the user terminal(111).

In some embodiments, the server (113) of the merchant redirects thecharge request to allow the user terminal (111) to communicate with theinterchange (101) to continue the payment process; and the user terminal(111) may provide (171) the account information (121) directly to theinterchange (101) after the charge request is redirected.

In alternative embodiments, the user may provide the account information(121) from the mobile phone (117) together with the approval of thecharge request.

In one embodiment, the interchange (101) communicates with the mobilephone (117) for the confirmation of the charge request via SMS messages.Alternatively, the confirmation and approval messages can be sent (173)via emails, instant messages, voice message, live calls from operators,etc.

In some embodiments, the user of the mobile phone (117) may choose tofulfill the charge request via the phone bill, instead of charging theaccount identified by the account information (121). Thus, after theconfirmation, the interchange (101) sends the premium messages to themobile phone (117) to collect funds via the phone bill of the mobilephone (117). In other embodiments, the interchange (101) may send aninstruction with the confirmation message to the mobile phone (117) toinstruct the user to send mobile originated premium messages to theinterchange (101) to collect the funds via the phone bill of the mobilephone (117).

FIG. 5 illustrates a user interface to associate an account with atelephone number according to one embodiment. In FIG. 5, the userinterface (180) includes a text field (183) that allows the user tospecify the phone number (123) with which the account information (121)provided in the text field (181) is to be associated.

In FIG. 5, the user interface (180) further includes an option list,which allows the user to select various types of accounts, such ascredit card accounts, bank accounts, charge card accounts, etc. In theexample illustrated in FIG. 5, the checkbox (185) is selected to specifya credit card account.

In some embodiments, the user interface (180) may further present a textfield (not shown in FIG. 5) to allow the user to specify an alias forthe account information (121) supplied in the text input field (181).For enhanced security, the alias can be used for subsequentcommunications with the user without revealing the account information(121).

In FIG. 5, the user interface (180) may be presented via a web browser(or a custom application) to submit account information (121) in thetext input field (181) from a user terminal (111) to the interchange(101). Alternatively, the account number can be submitted from themobile phone (117) via a message sent via SMS, WAP, voice mail, or viaan interactive voice response (IVR) system.

FIG. 6 illustrates another user interface to associate an account with atelephone number according to one embodiment. In FIG. 6, the userinterface (190) is presented on the mobile phone (117) of the user. Theuser interface (190) presents a message (191) from the interchange (101)to the mobile phone (117) at the phone number (123). The message (191)prompts the user to submit the account information (121) by providing areply message (193). The user may select the “send” button (195) toprovide the account information (121) for association with the phonenumber (123) or select the “cancel” button (197) to ignore the prompt.

In one embodiment, the messages (191 and 193) are transmitted to themobile phone (117) via a short message service (SMS). Alternatively, themessages can be transmitted to the mobile phone (117) via otherprotocols, such as multimedia message service (MMS), email, instantmessaging, WAP, voice mail, voice messages via an interactive voiceresponse (IVR) system, etc.

FIG. 7 illustrates a user interface to initiate a payment transactionaccording to one embodiment. In FIG. 7, the user interface (201)provides an option (205) to request the interchange (101) to process thepayment for the amount (203) required to make a purchase from the server(113) of a merchant.

In one embodiment, after the user selects the payment option (205), theserver (113) directs the request to the web server of the interchange(101), with a set of parameters to indicate the amount (203), theidentity of the merchant, a reference to the purchase, etc. Thus, theuser does not have to provide any personal information to the server(113) of the merchant to complete the payment process.

Alternatively, the user may provide the phone number to the merchant toprocess the payment. Thus, the user does not have to visit the websiteof the interchange (101) to complete the payment.

In one embodiment, the server (113) presents the payment option (205)via an online shopping cart system or a third party checkout system.Alternatively or in combination, the server (113) presents the paymentoption (205) via a web widget. For example, a web widget may include aprogram code that is portable and executable within a web page withoutrequiring additional compilation. The web widget allows the user toselect the option (205) to pay for the product and/or service withoutleaving the web page or refreshing the web page. In one embodiment, theinterchange (101) provides the web widget to facilitate the paymentprocessing.

FIG. 8 illustrates a user interface to initiate a payment requestaccording to one embodiment, after the payment request is redirected tothe website of the interchange (101). In FIG. 8, the user interface(201) includes the identity of the merchant and the amount (203) of therequested payment. The user interface (201) includes a text field (183)to allow the user to provide the phone number (123) to identify theaccount information (121) via its association with the phone number(123) in the data storage facility (107).

Further, user authentication may be used to reduce false messages to thephone number (123). For example, the user interface (201) may request aPIN for enhanced security. For example, the user may be required toregister with the interchange (101) prior to using the services of theinterchange (101); and after registering with the interchange (101), theuser is provided with the PIN or can created a customized PIN to accessthe functionality provided by the user interface (201).

Alternatively, the user interface (201) may request an identifierassociated with the phone number (123) to initiate the paymenttransaction. In some embodiments, the user interface (201) requires theuser to provide no information other than the phone number (123) in thetext field (183) to initiate the transaction.

In FIG. 8, the user interface (201) allows the user to select one optionfrom a plurality of payment options, including paying via the phonebill, and paying via one or more of the accounts identified by theaccount information (121) associated with the phone number (123) in thedata storage facility (107).

In some embodiments, the user interface (201) may present the paymentoptions after authenticating the user (e.g., via a personalidentification number or password) for enhanced security.

In some embodiments, the user interface (201) identifies the differentaccounts represented by the account information (121) by showing aliasesof the accounts. The aliases may be previously specified by the user, orbe dynamically generated by the interchange (101) based on the types ofthe accounts and/or portions of the account information (121) (e.g., thefirst or last few digits of the account number, etc.)

In one embodiment, once the user submits the payment request via theuser interface (201), the interchange (101) transmits a confirmationmessage to the mobile phone (117) according to the phone number (123)provided in the text field (183). In one embodiment, the interchange(101) transmits the confirmation to the mobile phone (117) after theuser is authenticated via the user interface (201) to reduce thepossibility of unauthorized/unwelcome messages to the mobile phone(117), which may occur when the user intentionally or unintentionallyprovides an unrelated phone number in the entry box (183).

FIG. 9 illustrates a user interface to confirm a payment requestaccording to one embodiment. In FIG. 9, the confirmation message (217)includes the amount (203) of the requested payment and the identity ofthe payee (e.g., a merchant operating the server (113)).

In one embodiment, the confirmation message (217) includes theinstruction to reply with a code, such as a code (e.g., “pay”) providedin the confirmation message (217) as illustrated in FIG. 9.

The presence of the code in the reply message is an indication of theuser approving the request; and the requirement for such a code in thereply eliminates false confirmations (e.g., generated via accidentalreplies or automated replies).

Alternatively or in combination, the requested code may include a PINassociated with the account, and/or a code (not shown) randomlygenerated and presented in the user interface used to initiate thepayment transaction (e.g., user interface (201)).

In some embodiments, the code requested in the text message (217) may bea personal identification number (PIN) associated with the phone number(123). The text message (217) does not include the code; and theknowledge of the code is an indication of the identity of the user.Thus, the use of such a code increases the security of the transaction.

In a further embodiment, the code requested in the text message (217)includes a code that is provided in response to the payment request(e.g., via the user interface (201), not shown in FIG. 8). The code maybe generated randomly at the time the request is received via the userinterface (201), or when the user interface (201) is presented to theuser. The code provided to the user interface (201) can be requested inthe reply received from the user interface (190) to indicate that theuser who is in possession of the mobile phone (117) has actual knowledgeabout the payment request submitted via the user interface (201).

After the correct reply is received, the interchange (101) communicateswith the account server (125) to electronically charge the user usingthe account information (121) and pays the payee using the fundscollected via communicating with the account server (125). Theinterchange (101) then notifies the user when the payment transaction iscomplete.

For example, the interchange (101) may notify the user via a textmessage to the mobile phone (117), as illustrated in FIG. 10. FIG. 10illustrates a user interface to confirm the completion of a paymenttransaction according to one embodiment. No reply to the message thatconfirms the completion of the payment transaction is necessary. Oncethe payment transaction is complete, the user would have access to theproduct purchased via the payment transaction.

In one embodiment, the interchange (101) stores an address of the userassociated with the phone number (123). After the completion of thepayment transaction, the interchange (101) provides the address to theserver (113) of the merchant for the delivery of the purchased product.In some embodiments, the user may provide multiple addresses associatedwith the phone number (123) and may select one as a delivery address inthe confirmation/approve message to the interchange (101).Alternatively, the interchange (101) may receive an address for productdelivery from the mobile phone (117) together with theconfirmation/approve message and then forward the address to the server(113) of the merchant. Thus, the shipping address of the transaction isverified to be associated with the mobile phone (117). In alternativeembodiments, the user may directly provide the shipping address in thewebsite hosted on the server (113) of the merchant.

In other embodiments, the user is provided with the options to pay viathe mobile phone bill associated with the phone number (123). Theinterchange (101) may dynamically calculate a set of premium messages,based on a set of limited number of predetermined prices for premiummessages, to match the purchase price. The interchange (101) sends theset of premium messages to the mobile phone (117) at the phone number(123) to collect the funds via the telecommunication carriers to pay forthe purchases. Thus, the purchase prices are not limited to the set ofpredetermined prices for premium messages. In some embodiments, theinterchange (101) may send the set of premium messages in a period oftime (e.g., a week, a month, a number of mouths, etc.) to spread thepayments over the period of time (e.g., to overcome budget limits and/orlimits imposed by regulations).

FIG. 11 illustrates a way to redirect a payment confirmation accordingto one embodiment. For example, after the user submits the paymentrequest to the interchange (101) via the user interface (201) shown inFIG. 8, the interchange (101) may present the user interface (201)illustrated in FIG. 11 to the user. The user interface (201) indicatesthat the request is being processed; and the user interface (201) isperiodically updated to show progress. Once the payment transaction iscompleted, the user interface (201) provides a confirmation message andmay automatically redirect the user back to the website of the payee(e.g., to access the purchased products or services).

In one embodiment, the user is required to provide the approval inresponse to the confirmation message (217), as illustrated in FIG. 9,within a predetermined period of time. If the user fails to provide theapproval from the mobile phone (117) within the predetermined period oftime, the payment request may be rejected; and the user interface (201)may present a message indicating the failure and then redirect the userback to the website of the payee.

In some embodiments, instead of redirecting the user back to the websiteof the payee after the expiration of a predetermined period of time(e.g., after the failure of the payment process, or after the completionof the payment), the user interface (201) may provide a link to thewebsite of the payee to allow the user to manually select the link to goback to the website of the payee to continue the process at the websiteof the payee.

FIG. 12 illustrates a user interface to receive payment optionsaccording to one embodiment. In FIG. 12, the interchange (101) sends amessage (217) to the mobile phone (117) to provide a number of optionsto the user. The message (217) identifies the amount (203) of therequested payment and the identity of the payee (e.g., a merchantoperating the server (113)) and asks the user to approve the paymentrequest via a reply that contains a selected payment option.

In FIG. 12, the user may reply with the code “1” to approve the paymentrequest and to pay via the phone bill of the mobile phone (117).Alternatively, the user may reply with the credit card information tocharge the payment to a credit card, as illustrated in FIG. 12.

In one embodiment, if the user provides credit card account informationin the approval message, the credit card account information is storedand associated with the phone number (123) in the data storage facility(107). Thus, in subsequent approval messages, the user does not have tosupply the same information again.

For example, the data storage facility (107) may store accountinformation for each of a plurality of account types (e.g., Visa,MasterCard, checking, savings, etc.) Thus, each of the accounts can beidentified to the user via the account type in the confirmation message,without revealing the details of the account information.

For example, the interchange (101) may combine the name of the financialinstitutions and the type of accounts to generate aliases for theaccount information.

In some embodiment, the user may define the aliases for the accountinformation by supplying the aliases with the account information (121)for association with the phone number (123).

FIG. 13 shows a method to process an online payment according to oneembodiment. In FIG. 13, the interchange (101) receives (301) an accountidentifier (e.g., 121) from a user and associates (303) the accountidentifier with a phone number (123) of the user in the data storagefacility (107). Over the Internet the interchange (101) subsequentlyreceives (305) a request for payment to be paid to a payee via themobile phone (117) identified by the phone number (123). In response tothe request, the interchange (101) transmits (307) a message (217) tothe mobile phone (117) to confirm the payment.

After receiving (309) a confirmation or approval from the mobile phone(117) for the payment, the interchange (101) electronically charges(311) the user an amount using the account identifier (e.g., viacommunicating with the account server (125) using the accountidentifier). The interchange (101) then transfers (313) the amount to apayee to fulfill the payment.

FIG. 14 shows another method to facilitate a payment transactionaccording to one embodiment. In FIG. 14, the interchange (101) receives(331) a request to pay an amount to a payee via a mobile phone (117).The interchange (101) transmits (333) a message (217) to the mobilephone (117) to confirm the request via the converter (131) correspondingto the controller (115) of the mobile phone (117).

After the interchange (101) receives (335) a confirmation with anaccount identifier (e.g., 121) from the mobile phone (117) for therequest, the interchange (101) electronically communicates (337) with afinancial institution to charge the user the specified amount using theaccount identifier. The interchange (101) pays (339) the payee accordingto the amount, optionally charges (341) the user a first fee to pay thepayee, and optionally charges (343) the payee a second fee forprocessing the payment.

In one embodiment, the users are given an incentive to provide theaccount information (121) for electronic payments via the accountservers (125). For example, the interchange (101) may charge a lower feefor fulfilling payment requests via the account server (125) than forfulfilling payments requests via the phone bill. For example, theinterchange (101) may offer rebates, discounts, etc. to the users whoprovide the account information (121). In some embodiments, theinterchange (101) can complete a payment process via the account server(125) with fewer restrictions than via the phone bill.

In one embodiment, the merchant may specify the second fee. Differentmerchants may offer different percentages of the purchase prices as thesecond fee; and the interchange (101) may calculate the first fee basedon the second fee offered by the merchant, by deducting the second feefrom the total fees to be charged (e.g., fees charged by thetelecommunication carrier for collecting the funds via the mobile phonebill associated with the telephone number and/or the fees charged by theinterchange (101) for processing the payments). Since the first fee ischarged to the customer (e.g., the purchaser of products and services),the cost to the customer can vary based on the selection of themerchant. For the same purchase prices, the first fee (and thus the costto the customer) may be different for purchases made via differentmerchants, because the merchants may offer different percentage of thepurchase price as the second fee. In some embodiments, the first andsecond fees include both fees charged by the telecommunication carrierfor collecting the funds via the mobile phone bill/account associatedwith the phone number (123) and the fees charged by the interchange(101) for processing the payments. In some embodiments, the first feeincludes the fees charged by the telecommunication carrier but no feescharged by the interchange (101). In some embodiments, the second feeincludes the fees charged by the telecommunication carrier but no feescharged by the interchange (101). In some embodiments, the first feeand/or the second fee do not include the fees charged by thetelecommunication carrier. In some embodiments, the first fee is notcharged; and in other embodiments, the second fee is not charged.

In one embodiment, a personal identification number (PIN) is used in theconfirmation of a transaction. The PIN may be stored in the user accounthosted on the data storage facility (107) of the interchange (101), andbe associated with the phone number (123) and/or the account information(121). For example, a user requesting a transaction using the fundsassociated with the phone number (123) may be required by theinterchange (101) to present the correct PIN associated with the phonenumber (123).

In some embodiments, the PIN may be the same as a PIN used by a thirdparty to control access to products and/or services for the user havingthe phone number (123). For example, the PIN for accessing the voicemail of the phone number (123) can be used by the interchange (101) toverify the identity of the user who attempts to use the funds associatedwith the phone number (123). For example, the interchange (101) mayreceive a PIN from the user and communicate with a telecommunicationcarrier of the phone number (123) to verify whether the received PIN isa correct PIN for accessing the voice mail of the phone number (123).

In some embodiments, a correct PIN is stored on the mobile phone (117)to control access to the services of the interchange (101). For example,an application running on the mobile phone (117) may prompt the user toprovide a PIN and check the PIN received from the user against thecorrect PIN stored on the mobile phone (117) to determine whether theuser is authorized to use the mobile phone (117) to access the servicesof the interchange (101). In some embodiments, the PIN is specific forthe control of access to the services of the interchange (101). Withoutthe PIN, the user may use other functions of the mobile phone (117),such as making phone calls, sending emails or text messages, etc. Whenit is determined that the user is authorized to use services of theinterchange (101) via the mobile phone (117), the application allows theuser to send a confirmation message to the interchange (101) to confirma transaction, or to display a code received from the interchange (101)for the confirmation of the transaction via presenting the code in a webpage of the interchange (101).

In some embodiments, the interchange (101) requires the user to providethe PIN associated with the phone number (123) via the mobile phone(117) at the phone number (123) to confirm a transaction. The user mayprovide the PIN to the mobile phone (117) which transmits the receivedPIN to the interchange (101) for verification. The user may provide thePIN in response to a message from the interchange (101) to the mobilephone (117) at the phone number (123), or in response to the interchange(101) presenting a request on the user terminal (111) to request theuser to send to the interchange (101) a confirmation message from themobile phone (117) at the phone number (123). Alternatively, the usermay provide the correct PIN in the user terminal (111) to obtain aconfirmation code, which is to be transmitted from the mobile phone(117) at the phone number (123) to confirm the transaction.

In some embodiments, the user may provide the correct combination of thePIN and the phone number (123) to the user terminal (111) to request atransaction, without the need to further confirm the request via themobile phone (117).

In one embodiment, to further improve security, the communications fromthe mobile phone (117) at the phone number (123) further include anidentification number stored on the mobile phone (117) (e.g., in anintegrated circuit (IC) chip). For example, a software program (e.g., aJava application) can be used to read a hardware identification numberfrom the IC chip of the mobile phone (117) and transmit a confirmationmessage including the hardware identification to indicate that themessage is indeed from a mobile phone (117) registered with the user.

In one embodiment, the International Mobile Equipment Identity (IMEI) ofthe mobile phone (117) is used as the hardware identification number.Alternatively, a hardware identification number may be assigned to andstored into the mobile phone (117) when the mobile phone (117) isinitially configured for the services of the interchange (101) (e.g.,when the application is installed on the mobile phone (117)).

In one embodiment, when the mobile phone (117) at the phone number (123)is registered for the services of the interchange (101), a softwareapplication is installed and/or configured on the mobile phone (117).The software application can be implemented using Java programminglanguage in one embodiment. Other programming languages can also beused. Further, in some embodiments, the application can be implementedvia hardware circuits, such as Application-Specific Integrated Circuit(ASIC) or Field-Programmable Gate Array (FPGA), or a combination ofspecial purpose hardware circuits and instructions.

In one embodiment, the application is configured on the mobile phone(117) to present a user interface (350) to confirm a transactionaccording to one embodiment, as illustrated in FIG. 15. In FIG. 15, theapplication communicates with the interchange (101) to presentinformation that identifies aspects of the transaction, such as thepayee, the amount involved in the transaction, a description of theproduct or service in the transaction, etc.

In FIG. 15, the user interface (350) includes an entry box (353) toreceive a PIN from the user. When the PIN received in the user interface(350) is invalid, the user interface (350) may reject the input andprevent the user from sending the confirmation message via the userinterface (350).

Alternatively, the user interface (350) may accept the user inputwithout checking the input for validity and transmit the confirmationwith the received PIN to the interchange (101). The interchange (101)then checks the received PIN for validity. If the interchange (101)determines that the received PIN is valid for the phone number (123) ofthe mobile phone (117), the interchange (101) accepts the confirmationand performs the requested transaction. If the interchange (101)determines that the received PIN is invalid, the user interface (350)may prompt the user to re-enter the PIN.

In some embodiments, the user interface (350) and/or the interchange(101) may prevent the user from using the user interface (350) after theuser fails to provide the correct PIN after a predetermined number ofattempts.

In FIG. 15, the user interface (350) further includes an entry box forthe user to enter a code (351) that represents the transaction. Forexample, when the user uses the user terminal (111) to submit atransaction request (e.g., via a web browser), the interchange (101)provides the code (351) as an identifier of the transaction.

In one embodiment, after the user enters the code (351) in the entrybox, the application running the user interface (350) communicates withthe interchange (101) to obtain the information about the transaction,such as the payee, the amount of the transaction, a description, etc.Thus, providing the code (351) in the entry box allows the user to seein the user interface (350) the information specific to the transactionfor the confirmation of the correct transaction.

In one embodiment, the code (351) is a one-time code, which expiresafter the code is submitted to the interchange (101). To improvesecurity, the interchange (101) may cause the one-time code (351) toexpire after a predetermined period of time from when the one-time code(351) is provided by the interchange (101) to the user. When theone-time code (351) or the PIN is incorrect, the interchange (101)rejects the confirmation. After an incorrect combination of the PIN andthe one-time code (351) is received, the interchange (101) may cause theone-time code (351) to expire; and the user is prompted to resubmit thetransaction request to obtain a new one-time code.

In some embodiments, the interchange (101) may allow the user interface(350) to resubmit the input for the PIN a number of times if theone-time code (351) is valid. For example, the user interface (350) maybe presented in response to a message from the interchange (101)requesting the confirmation of the transaction. The one-time code (351)is required in the entry box to ensure that the user has knowledge aboutthe transaction submitted via the user terminal (111). The PIN isrequired in the entry box (353) to ensure that the user is authorized.In some embodiments, the one-time code (351) is optional.

In some embodiments, the interchange (101) provides the one-time code(351) to the user via the user interface (350). The application may sendthe one-time code (351) back to the interchange (101) to identify thetransaction being confirmed by the user.

Alternatively, the interchange (101) may require the user to provide theone-time code (351) back to the interchange (101) via the user terminal(111) that submits the corresponding transaction request. After theone-time code (351) shown in the user interface (350) on the mobiledevice (117) is transmitted from the user terminal (111) to the webserver of the interchange (101), the transaction is confirmed with theinterchange (101).

In one embodiment, the PIN is used to protect access to the one-timecode (351). The user interface (350) is configured to display theone-time code (351) after the user enters the correct PIN in the entrybox (353). If the user fails to enter the correct PIN in the entry box(353), the user interface (350) does not display the one-time code (351)which is required in the user terminal (111) to confirm the transaction.

In one embodiment, the code (351) is a one-time password, which isgenerated on the mobile phone (117). The one-time password is providedto the interchange (101) to confirm the transaction (e.g., via themobile phone (117) communicating with the interchange (101), or via theuser terminal (111) communicating with the interchange (101)).

In one embodiment, the one-time password is generated on the mobilephone (117) after the request for the transaction is submitted to theinterchange (101) via the user terminal (111). The one-time password isnot received in the mobile phone (117) from the interchange (101) as aresult of the transaction request. In one embodiment, the one-timepassword is generated based at least in part on a seed that isconfigured in the mobile phone prior to the transaction.

In one embodiment, the one-time password is generated on the mobilephone (117) after the PIN is verified in the entry box (353). If the PINentered in the entry box (353) is invalid, the mobile phone (117) doesnot generate the one-time password.

In one embodiment, the user is instructed to use the one-time passwordto authenticate with the interchange (101), using the user terminal(111) that submits the request for the transaction. Alternatively, themobile phone (117) may transmit the one-time password to confirm thetransaction. In some embodiments, the mobile application generates theone-time password and transmits the one-time password to the interchange(101) to confirm the transaction, without displaying the one-timepassword to the user, after the user enters the correct PIN.

In one embodiment, the correct PIN is stored on the mobile phone (117)(e.g., in an encrypted format). Thus, the user interface (350) canverify the PIN entered in the entry box (353) without communicating withthe interchange (101).

Alternatively, the correct PIN may be stored on the data storagefacility (107) of the interchange (101). The application running on themobile phone (117) communicates the PIN received in the entry box (353)to the interchange (101) (e.g., in an encrypted format) forverification.

Alternatively, a third party may store the correct PIN (e.g., forcontrolling access to the voice mail of the phone number (123)). Afterthe interchange (101) obtains the PIN received in the entry box (353),the interchange (101) communicates with the third party to verify thePIN.

FIG. 16 illustrates a mobile phone configured to confirm transactionsaccording to one embodiment. In FIG. 16, the mobile phone (117) includesa hardware identification number (396) which identifies the mobile phone(117). In one embodiment, the hardware identification number (396) isconfigured and stored on the mobile phone (117) prior to the mobilephone (117) being distributed to end users. For example, the hardwareidentification number (396) may include International Mobile EquipmentIdentity (IMEI) and/or Media Access Control address (MAC address).

In some embodiments, the hardware identification number (396) includes anumber that is assigned to the mobile phone (117) when the mobile phone(117) is registered with the interchange (101) for the services providedby the interchange (101). For example, the interchange may use anapplication to write the assigned number into an integrated circuit (IC)chip in the mobile phone to identify the mobile phone (117). In someembodiments, the assigned number is written into a removable memorymodule to represent the registered mobile phone (117).

In FIG. 16, the mobile phone (117) includes a seed (363) for theone-time password generator (361). The one-time password generator (361)is configured to generate a series of passwords for authenticating withthe interchange (101), based on the seed (363) and/or the current time.Thus, the one-time password generated on the mobile phone (117) is insynchronization with the corresponding one-time password generated orused on the interchange (101). Alternatively, the one-time passwordgenerator (361) may not rely upon the current date and time forsynchronization; and the interchange (101) is configured to tolerateskipping of up to a predetermined number of one-time passwords to accepta one-time password from the mobile phone (117).

In one embodiment, the PIN verifier (365) is configured to check the PINreceived in the entry box (353) against the PIN (367) stored on themobile phone (117). After the PIN verifier (365) determines that thereis a match between the PIN (367) stored on the mobile phone (117) andthe PIN received in the entry box (353), the communication subsystem(37) transmits a one-time password obtained from the one-time passwordgenerator (361) and the hardware identification number (396) to theinterchange (101) to confirm the transaction. In one embodiment, theone-time password is used to encrypt the confirmation transmitted fromthe mobile phone (117) to the interchange (101) to confirm thetransaction.

The mobile phone (117) may transmit the confirmation message to theinterchange (101) via short message service (SMS), email, a WAP request,or a web request. Other communication protocols can also be used.

FIGS. 17-19 illustrate methods to confirm transactions according to oneembodiment.

In FIG. 17, neither the interchange (101) nor the mobile phone (117)stores the correct PIN associated with the phone number of the mobilephone (117). A third party (373) stores the correct PIN associated withthe phone number (123) of the mobile phone (117). To confirm atransaction, the interchange (101) transmits a message to the mobilephone (117) at the phone number (123) to request a confirmation messagefrom the mobile phone (117). The mobile phone (117) presents a userinterface (e.g., 350) to receive an input for the PIN from the user(371) and transmits the received PIN to the interchange (101), whichfurther communicates with the third party (373) to verify whether thereceived PIN matches the correct PIN. Thus, the user may use the samePIN for multiple services associated with the phone number (123), suchas accessing voice mail at the phone number (123) and paying forpurchases using funds associated with the phone number (123).

In FIG. 18, after a request for a transaction between a first party anda second party (431) is received in the interchange (101) (e.g., via aweb server), the interchange (101) communicates (433) with the mobilephone (117) at a phone number (123) identified in the request to confirmthe transaction, via checking a PIN associated with the phone number(123). The transaction is confirmed if a PIN entered into the mobilephone (117) by the user of the mobile phone (117) is correct. After thetransaction is confirmed, the interchange (101) collects (435) funds forthe transaction via transmitting premium messages to the mobile phone(117).

In FIG. 19, the interchange (101) provides (451) instructions and datato a mobile phone (117) at a phone number (123) to configure the mobilephone (117) for the services of the interchange (101). The instructionsmay be in Java programming language, or other programming languages. Thedata may include a seed (363) for the one-time password generator (361)and/or a portion of the hardware identification number (396). Forexample, the user may use the mobile phone (117) to download theinstructions and data from the interchange (101).

After the mobile phone (117) is configured via the instructions anddata, the interchange (101) may receive (453) a request identifying thephone number (123) and transmit a message to the user (371) to cause themobile phone (117) to execute (455) the instructions on the mobile phone(117) to present a user interface (350). After the identify of the user(371) is verified (457) based on a PIN entered into the user interface(350), the mobile phone (117) generates (459) a one-time password on themobile phone (117) and transmits (461) the one-time password to theinterchange (101) to confirm the request. Once the request is confirmedvia the confirmation transmitted from the mobile phone (117), theinterchange (101) provides (463) a payment according to the request(e.g., using funds associated with the phone number (123)).

In one embodiment, the interchange (101) includes a server computer. Theserver computer may be used to receive a request for a transactionbetween a first party and a second party. The request includes theindication of a phone number of the first party and an amount to be paidto the second party.

In response to the request, the server computer communicates with amobile phone (117) at the phone number (123) to confirm, via a personalidentification number of the first party, the transaction. After thetransaction is confirmed via the personal identification number of thefirst party, the server computer transmits one or more premium messagesto the mobile phone (117) to collect, via a telecommunication carrier ofthe mobile phone (117), funds in accordance with the amount to be paidto the second party.

In one embodiment, the interchange (101) provides instructions to themobile phone (117). When executed, the instructions cause the mobilephone (117) to present a user interface to receive a first personalidentification number.

The instructions may further cause the mobile phone (117) to encrypt thefirst personal identification number for transmission from the mobilephone (117) to the server computer. The server computer is to comparethe first personal identification number with a second personalidentification number associated with the phone number (123) of themobile phone (117) to determine whether the transaction is confirmed.

Alternatively, the instructions may further cause the mobile phone (117)to compare the first personal identification number with a secondpersonal identification number stored on the mobile phone (117) todetermine whether the first personal identification number is correct.After determining that the first personal identification number iscorrect, the instructions further cause the mobile phone (117) totransmit a message to the server computer to confirm the transaction.

In one embodiment, the instructions further cause the message to includea hardware identification code of the mobile phone (117). The hardwareidentification code may be provided to the mobile phone (117) in aread-only memory, before the mobile phone (117) is distributed to an enduser. For example, the hardware identification code may includeInternational Mobile Equipment Identity (IMEI).

In some embodiments, the hardware identification code is provided to themobile phone (117) when the mobile phone (117) is registered with theserver computer for services offered by the server computer.

In one embodiment, the instructions further cause the mobile phone (117)to transmit the message to the server computer via short message service(SMS). In some embodiments, the message includes a one-time passwordgenerated via the instructions. For example, the one-time password canbe generated based on a current time; and the server computer is todetermine whether the one-time password is generated by the mobile phone(117). When the one-time password matches a series of passwordsconfigured to be generated by the mobile phone (117), the one-timepassword is accepted. In one embodiment, the server computer provides tothe mobile phone (117) at the phone number (123), a seed for generationof the one-time password, which is used by the instructions to generatethe one-time password.

In one embodiment, the server computer provides the first party with aseed for one-time password generation when the first party registers forservices of the server computer; and the instructions cause the mobilephone (117) to present a user interface to receive the seed.

In one embodiment, the server computer is to further communicate with athird party to determine whether the first personal identificationnumber received in the user interface is associated with the phonenumber (123) of the mobile phone (117). For example, the third party maybe a telecommunication carrier of the mobile phone (117); and a correctpersonal identification number is used by the telecommunication carrierto control access to voice mails for the phone number (123).

In one embodiment, the request is received in a web server of the servercomputer; the server computer communicates with the mobile phone (117)to provide a one-time code to the mobile phone (117), after the personalidentification number of the first party is verified via the mobilephone (117); and the server computer is configured to receive theone-time code back in the web server to confirm the transaction.

In one embodiment, the request is received in a web server of the servercomputer; the server computer provides a one-time code via the webserver to the first party; and the server computer is configured todetermine whether the transaction is confirmed based on receiving, fromthe mobile phone (117), both the personal identification number of thefirst party and the one-time code.

In one embodiment, the interchange (101) is used to facilitate userauthentication for signing in accounts on servers (113) that may beoperated by entities different from the entity that operates theinterchange (101). The interchange (101) can also be used for userauthentication at a server (113) when the server (113) is operated bythe same entity that operates the interchange (101).

For example, in one embodiment, a user can provide a mobile phone number(123) to identify the user for signing into an account-based servicehosted on the server (113). The user can use the mobile phone number(123) to make a request to login; and the interchange (101) communicateswith the mobile phone (117) at the mobile phone number (123) toauthenticate the identity of the user for the system hosted on theserver (113). The user can use the mobile phone (117) to complete theauthentication to access an application or service.

The mobile phone number (123) can be tied or bound to existing accountsand/or new accounts of the user, hosted on various servers (113), forauthentication purposes. These accounts may have different typedefinitions and can vary depending on system setup. For example, theuser can use the mobile phone number (123) to authenticate/login to abank account, an online account, a credit card account, a checkingaccount, an email account, etc. In one embodiment, the interchange (101)provides an Internet-based service to authenticate a mobile phone number(123) to an account and verify the identity of the user (e.g., usingtwo-factor authentication or multi-factor authentication).

In one embodiment, the interchange (101) is further used to providepayments to the servers (113) for accessing the accounts or foraccessing premium contents or features through the accounts. Theinterchange (101) may be used to pay for the purchases made via theaccounts. Alternatively, the interchange (101) may provide theauthentication service without having to use the funds associated withthe mobile phone number (123) to make payments on behalf of the user.

FIG. 20 shows a user interface to sign a user in according to oneembodiment. In FIG. 20, the user interface is presented via a browserwindow (501) on the user terminal (111). The user interface allows theuser to sign in by providing the username (505) and the password (507)and selecting the “sign in” button (503). In addition, the user is alsoallowed to select the button (509) to sign in via the mobile phone (117)of the user.

In some embodiments, the server (113) may not allow the user to sign inusing the username (505) and the password (507) and may require the userto sign in via the mobile phone (117) of the user. Thus, the users ofthe server (113) do not have to use the username (505) and the password(507) created specifically for the server (113).

In one embodiment, after the user selects the button (509), the server(113) redirects the user to a website of the interchange (101) forauthentication, as illustrated in FIG. 21.

FIG. 21 shows a user interface to obtain a phone number to sign a userin according to one embodiment. In FIG. 21, the website of theinterchange (101) promotes the user to provide or verify the phonenumber (123) in the entry box (511).

In one embodiment, the website of the interchange (101) uses a browsercookie to store the phone number (123). Thus, after the user providesthe phone number (123) in the entry box (511) to sign in one account viathe interchange (101), the web page as illustrated in FIG. 21 can usethe browser cookie to store the phone number (123) and automaticallyfill in the entry box (511) when the user is again redirected to thewebsite of the interchange (101) (e.g., by the same server (113) to signin the same account, or a different server to sign in a differentaccount).

In another embodiment, the phone number (123) is provided by the webpage after the user first provides the phone number (123) in the entrybox (511) during a previous session of visiting the website of theinterchange (101). The interchange (101) stores the phone number (123)in connection with an identification of the session such that when theuser is redirected back to the website of the interchange (101) in thesame session, the interchange (101) can automatically fill the entry box(511) with the phone number (123) previously provided in the session.

In one embodiment, when the user selects the button (513), theinterchange (101) communicates with the mobile phone (117) at the phonenumber (123) to authenticate the user. For example, the interchange(101) can transmit a text message to the mobile phone (117) to requestthe PIN of the user from the mobile phone (117) at the phone number(123).

In some embodiments, the interchange (101) may require the user to signin to the website of the interchange (101) (e.g., using a username and acorresponding password), when the phone number (123) is first receivedin the entry box (511) for a browser session. Such a requirement may beused to reduce or eliminate unintended spamming by the interchange(101), due to the user entering in the text entry box (511) a phonenumber that does not belong to the user. After the user signs in to thewebsite of the interchange (101), the interchange (101) may pre-fill theentry box (511) based on profile information about the user stored onthe data storage facility (107) of the interchange (101).

In some embodiments, the interchange (101) further authenticates theuser via communicating with the mobile phone (117) at the phone number(123). For example, the interchange (101) can transmit a text message tothe mobile phone (117) to request the PIN of the user from the mobilephone (117) at the phone number (123) to complete signing in to thewebsite of the interchange (101).

In one embodiment, when the user is returning to a valid, previouslyauthenticated browser session for the authentication process of a server(113), the interchange (101) may skip communicating with the mobilephone (117) for the authentication of the user. For example, when theuser is retuning to a valid browser session on the website of theinterchange (101) for signing into the server (113), the interchange(101) may request the user to present the password for the website ofthe interchange (101); and if the correct password is received, themobile phone (117) may rely upon the previous communication with themobile phone (117) in the valid browser session to complete theauthentication for the server (113), without a new communication withthe mobile phone (117) to confirm the identity of the user.

Alternatively, when the user is returning to the valid, previouslyauthenticated browser session for the authentication into the server(113), the interchange (101) may skip the authentication via usernameand password on the website of the interchange (101), but still requirethe user to confirm identity via the mobile phone (117) at the phonenumber (123).

In some embodiments, when the user is returning to the valid, previouslyauthenticated browser session for the authentication into the server(113), the interchange (101) may skip the need to further authenticatethe user via the website of the interchange (101) and/or via the mobilephone (117).

In some embodiments, after the interchange (101) confirms the identityof the user via the mobile phone (117), the user on the user terminal(111) is signed in to the website of the interchange (101) until theuser signs out, or the session is closed or expires.

In other embodiments, the interchange (101) may not require the user tosign in to the website of the interchange (101).

FIG. 22 shows a mobile user interface to confirm the identity of a useraccording to one embodiment. In FIG. 22, the user interface (521) ispresented on the mobile phone (117) at the phone number (123) specifiedby the user to sign in. The message (523) presented in the userinterface (521) identifies the server (113) (e.g., www.songs.com) whichrequested the interchange (101) to authenticate the user. The interface(521) requires the user to provide the PIN (525) to confirm the identityof the user.

In one embodiment, after the user selects the “sign in” button (527) inFIG. 22, the interchange (101) verifies the PIN (525) received via themobile phone (117). If the correct PIN (525) is received from the mobilephone (117), the interchange (101) provides information to the server(113) to allow the user to sign in an account on the server (113).

In one embodiment, the user account on the server (113) is identified bythe phone number (123) and/or the PIN (525). For example, in oneembodiment, the phone number (123) is directly used to specify theaccount on the server (113). For example, a hash of the phone number(123), the PIN (525) and/or the identity of the server (113) can be usedto represent the account of the user on the server (113).

In some embodiments, the phone number (123), the PIN (525) and/or theidentity of the server (113) are used to look up an identifier of theaccount of the user on the server (113).

For example, in one embodiment, when a new account is created on theserver (113) for the user, the user is redirected to the website of theinterchange (101) for authentication or confirmation (e.g., via a userinterface similar to that shown in FIG. 21). After the user request tocreate the new account is confirmed via the mobile phone (117), the useraccount is associated with the mobile phone (117) and/or the PIN (525).

For example, in one embodiment, when the user is redirected to thewebsite of the interchange (101) for the confirmation, the identifier ofthe account can be provided from the server (113) to the website of theinterchange (101) via the URL that redirected the request. After theinterchange (101) receives the PIN (525) from the mobile phone (117),the identifier of the account is stored in the data storage facility(107) as part of the account info (121) associated with the phone number(123) and/or the PIN (525). In one embodiment, the account identifier iscommunicated from the server (113) to the interchange (101) via the webbrowser of the user in an encrypted format to prevent tampering and forincreased security.

Alternatively, the server (113) may communicate the account identifierto the interchange (101) directly, without going through the userterminal (111). For example, the server (113) may provide a sessionidentifier, or a request identifier, to the interchange (101) when theserver (113) redirects the user to the website of the interchange (101).The server (113) separately communicates the account identifierassociated with the session identifier, or the request identifier,directly to the interchange (101) (e.g., via an Application ProgrammingInterface, or a web service). The session identifier, or the requestidentifier, thus allows the interchange (101) to associate the accountidentifier with the phone number (123) provided by the user.

In some embodiments, an existing account of the user can also be linkedto the phone number (123) of the user in a similar way as linking a newaccount to the phone number (123).

In some embodiments, the server (113) may request the user to providethe correct username (505) and the password (507) in the user interfacesimilar to that illustrated in FIG. 20, before the user is authenticatedvia the mobile phone (117). After the server (113) authenticates theuser via the username (505) and the password (507), the server (113)requests the interchange (101) to further authenticate the user via themobile phone (117). For example, in one embodiment, the button (509) isnot displayed; and when the “sign in” button (503) is selected, thebrowser is directed or redirected to the website of the interchange(101) for authentication via the mobile phone (117).

In one embodiment, the server (113) may store the phone number (123) inthe account of the user; and after the user is authenticated via theusername (505) and the password (507), the server (113) may communicatewith the interchange (101) in the background to request the interchange(101) to further authenticate the user via the mobile phone (117).

In some embodiments, the user may provide the phone number (123) to theserver (113) to identify the account of the user; and the server (113)communicates with the interchange (101) in the background to request theinterchange (101) to authenticate the user via the mobile phone (117),without redirecting the user to the website of the server (113), asillustrated in FIG. 23.

FIG. 23 shows another user interface to sign a user in according to oneembodiment. In FIG. 23, the server (113) provides a user interface inthe browser window (501). After the user provides the phone number (123)in the entry box (511) in the browser window (501), the user may selectthe “sign in” button (503) to request access. Before the server (113)allows the user to access the restricted areas of the account associatedwith the phone number (123) provided in the entry box (511), the server(113) communicates with the interchange (101) for user authenticationvia the mobile phone (117) at the phone number (123). For example, theuser may be required to provide a PIN associated with the phone number(123) to pass the authentication process; the user may be provided witha one-time code via a web page presented in the web browser (501) and beinstructed to provide the one-time code back to the interchange (101)via the mobile phone (117) at the phone number (123); and/or the usermay be provided with a one-time code via the mobile phone (117) at thephone number (123) and instructed to provide the one-time code back tothe website of the server (113) via the web browser (501). In someembodiments, the one-time password generated on the mobile phone (117),as discussed above, can be used in the authentication process.

In some embodiments, after the user selects the “sign in” button (503)in FIG. 23, the user is redirected to the website of the interchange(101) for a user interface as illustrated in FIG. 21.

In some embodiments, the user interface as illustrated in FIG. 21 ispresented as a portion of the login page of the server (113).

In one embodiment, the user may initiate the login process via visitinga web page of the interchange (101), on which the userselects/identifies the server (113) the user wants to access andprovides the phone number (123) to initiate the mobile phone (117) basedon the authentication. After the interchange (101) completes the userauthentication via the mobile phone (117) at the phone number (123), theinterchange (101) identifies the account of the user at the server (113)and forwards the user to the server (113). The server (113) may or maynot further authenticate the user.

In one embodiment, the user can sign in a browser session with a websiteof the interchange (101), authenticated via the mobile phone (117). Fromthe authenticated session on the website of the interchange (101), theuser can be forwarded to various different accounts of the user hostedon different servers (113), with or without being further authenticatedby the respective servers (113). The interchange (101) automaticallyidentifies the accounts of the user, based on the phone number (123)and/or the PIN of the user, to forward the user to the respectiveaccounts on the servers (113).

In one embodiment, multiple users may share the same phone number (123)to access different, individual accounts of the users. The interchange(101) is configured to distinguish the user via different PINs of theusers and/or different user identifiers. Alternatively, the interchange(101) may use only the phone number (123) to identify the user; andusers not sharing the same accounts are required to use different phonenumbers for mobile phone based authentication.

FIG. 24 shows a system to sign a user in according to one embodiment. InFIG. 24, the interchange (101) has a data storage facility (107) tostore account information (121) associated with the phone number (123).The account information (121) may include a PIN associated with thephone number (123), data for a one-time password generated on the mobilephone (117) at the phone number (123) (e.g., the seed for the generationof one-time passwords), a one-time code presented to the user (e.g., viathe web browser (501) or via the mobile phone (117)) that is to bereceived back from the user, the account identifiers of the user ondifferent servers (113), etc.

In FIG. 24, the user (371) may use the user terminal (111) to sign inthe account (531) hosted on the server (113). To authenticate the user(371), the interchange (101) transmits a message to the mobile phone(117) at the phone number (123) to request a PIN from the user (371).When the PIN received via the mobile phone (117) matches with theaccount information (121) stored on the data storage facility (107), theinterchange (101) provides information to the server (113) to allow theuser (371) to access the account (531) using the user terminal (111),which is typically a device distinct and separate from the mobile phone(117).

In some embodiments, the PIN received from the mobile phone (117)includes a one-time password received from the mobile phone (117). Insome embodiments, the PIN includes a one-time code provided to the user(371) via the user terminal (111). In other embodiments, a one-time codeis provided to the user (371) via the authentication message from theinterchange (101) to the mobile phone (117); and the user (371) isrequested to provide the one-time code back to the interchange (101) viathe user terminal (111) (e.g., via the server (113), or directly to thewebsite of the interchange (101)).

In one embodiment, the interchange (101) looks up the identifier of theaccount (531) from the account information (121), based on the phonenumber (123) and/or the PIN. The interchange (101) provides the accountidentifier to the server (113) to allow the user (371) to access theaccount (531) identified by the account identifier.

In some embodiments, the user (371) has multiple accounts on the server(113) that are associated with the phone number (123). The interchange(101) identifies the accounts to the server (113) to allow the user(371) to access any of the accounts, after the identity of the user(371) is verified via the mobile phone (117).

In one embodiment, the server (113) is configured to identify theaccount (531) based on the phone number (123); and the interchange (101)may communicate with the server (113) to indicate whether the user (371)failed or succeed in passing the authentication process.

FIG. 25 shows a method to sign a user in according to one embodiment. InFIG. 25, the interchange (101) receives (541) a request to authenticatea user (371) to sign the user (371) in an account (531). The interchange(101) communicates (543) with a mobile phone (117) of the user (371) ata phone number (123) specified by the user (371) to confirm the identityof the user (371). The interchange (101) provides (545) information tothe server (113) to allow the user (371) to sign in the account (531) onthe server (113), if the identity of the user (371) is confirmed via theinterchange (101) communicating with the mobile phone (117).

In one embodiment, the request includes a web request from a browser(501) of the user (371), redirected from the host of the account (531)(e.g., server (113)) to the website of the interchange (101).

In one embodiment, the interchange (101) provides a user interface onthe browser (501) of the user (371) to receive the phone number (123)specified by the user (371), as illustrated in FIG. 21.

In one embodiment, in communicating with the mobile phone (117), theinterchange (101) receiving a personal identification number (PIN) fromthe mobile phone (117) of the user (371); and the identity of the user(371) is not confirmed by the interchange (101) if the PIN is notassociated with the phone number (123) prior to the receiving of therequest.

In one embodiment, the interchange (101) redirects the web browser (501)from the website of the interchange (101) to the server (113) hostingthe account (531); and the information provided by the interchange (101)to the sever (113) includes an identifier to uniquely represent the user(371) among a plurality of users (or to uniquely identify the account(531) among a plurality of accounts hosted on the server (113)). In oneembodiment, the identifier is generated from hashing the mobile phonenumber (123) and the PIN; in another embodiment, the identifier ispre-associated with the phone number (123) and the host.

In one embodiment, the account (531) is a new account of the user (371)created on the server (113) hosting the account (531); and theinformation provided from the interchange (101) to the server (113)associates the account identifier with an identifier representing theuser (371). Subsequently, when the user (371) is authenticated by theinterchange (101) via the mobile phone (117), the interchange (101)indicates to the server (113) that the user (371) represented by theuser identifier has passed the authentication process, which allows theserver (113) to grant the user (371) access to all accounts hosted onthe server (113) and associated with the user identifier.

In one embodiment, the information is provided by the interchange (101)to the server (113) hosting the account (531) without going through theuser (371). Alternatively, the information provided by the interchange(101) to the server (113) hosting the account (531) is communicated viaredirecting the web browser (501) of the user (371).

In one embodiment, the request includes an identification code toidentify a session initiated on the server (113) hosting the account(531) to sign in the user (371); and the information provided from theinterchange (101) to the server (113) includes the identification code.

In one embodiment, the user (371) has a plurality of accounts on theserver (113); and the information provided from the interchange (101) tothe server (113) allows the user (371) to access the plurality ofaccounts.

In one embodiment, the interchange (101) determines an identifier of theaccount (531) based on the communicating with the mobile phone (117),and provides the identifier of the account (531) of the user (371) tothe server (113) to allow the user (371) to access the account (531).

In one embodiment, the interchange (101) receives (541) the request,including the phone number (123), from the server (113) without goingthrough the user (371). For example, based on the username identified bythe user (371), the server (113) may look up the phone number (123) fromthe account (531) associated with the username to request theinterchange (101) to authenticate the user (371) on behalf of the server(113). In some embodiments, the server (113) receives from the user(371) the phone number (123) as the username to access the account(531).

In one embodiment, the account (531) is funded by funds associated withthe phone number (123) and paid by the interchange (101) to the server(113) on behalf of the user (371). For example, in one embodiment, theinterchange (101) transmits one or more premium messages to the mobilephone (117) to collect the funds.

In one embodiment, the information allows the user (371) to sign in theaccount, without the user (371) paying the server (113) via theinterchange (101).

In one embodiment, the account (531) hosted on the server (113) allowsthe user (371) to access at least one of: email, instant messaging,social networking, blogging, banking, online shopping, gaming, onlinecommunication, and content sharing.

FIGS. 26-29 show methods to approve a payment transaction according tosome embodiments.

In FIG. 26, after the interchange (101) confirms (641) an identity of auser of a user terminal (111), the interchange (101) receives (643) fromthe user terminal (111) a request to pay via a phone number (123) of theuser. In one embodiment, the interchange (101) confirms the identify ofthe user of the user terminal (111) and/or associates the identity ofthe user of the user terminal (111) with the phone number (123) of themobile phone (117) prior to the user submitting a request to pay via thephone number (123). Thus, communications with the mobile phone (117) atthe phone number (123) for the confirmation and/or approval of therequest does not have to take place between the request and the paymentoperation; and thus the delay between the request and the paymentoperation can be reduced.

For example, the user terminal (111) may include a web browser; and theuser may log into a web server of the interchange (101) using the webbrowser. The interchange (101) may prompt the user via the web browserrunning on the user terminal (111) to provide the phone number (123) anda password associated with the phone number (123). After verifying thepassword, the user is logged into a session tracked by the web browseron the user terminal (111); and the web browser running on the userterminal (111) is associated with the phone number (123).

In one embodiment, the interchange (101) further communicates with themobile phone (117) at the phone number (123) to complete theverification process. For example, the interchange (101) may send aone-time verification code to the mobile phone (117) at the phone number(123) and request the user to provide the correct one-time verificationcode back via the user terminal (111) to verify the association betweenthe user terminal (111) and the phone number (123). Alternatively, theinterchange (101) may provide the one-time verification code to the userterminal (111) and instruct the user to communicate the code back to theinterchange (101) via the mobile phone (117) at the phone number (123).Alternatively, after the user logs in using the user terminal (111), theinterchange (101) may send a message to the mobile phone (117) torequest a reply from the mobile phone (117) at the phone number (123)within a predetermined period of time to validate the session. In someembodiments, after the user provides the phone number (123) to theinterchange (101) using the user terminal (111), the user is instructedto provide the password via the mobile phone (117) to complete the login process.

In one embodiment, the user terminal (111) tracks the session. Forexample, the user terminal (111) may use a web browser to track thesession via information maintained by the web browser (e.g., cookies).Alternatively, or in combination, the interchange (101) may track thesession by maintaining information on the data storage facility (107).For example, after the user completes the log in process, theinterchange (101) may identify the user terminal (111) via identifierssuch as Internet address, Media Access Control address (MAC address), adifferent phone number (e.g., when the user terminal is a differentmobile phone), or other software or hardware identification numberassociated with the user terminal (111), such as a digital certificate;and the interchange (101) may associate the phone number (123) with suchidentifiers until the expiration of a predetermined time period, orafter the user signals an end of the session using the user terminal(111) or using the mobile phone (117) at the phone number (123). In oneembodiment, the interchange (101) associates a plurality of identifiersof the user terminal (111) with the phone number (123) for the session.When at least one of the identifiers of the user terminal (111) ischanged, the interchange (101) may terminate the session automatically.

In FIG. 26, after the user terminal (111) submits the request to pay viathe phone number (123), the interchange (101) approves (645) the requestbased on the confirming of the identity of the user performed prior tothe request and processes (647) the request using funds associated withthe phone number (123). For example, the interchange (101) may transmitpremium messages, via a corresponding converter (131), to a mobile phone(117) at the phone number (123) to collect the funds, or receive premiummessages from a mobile phone (117) at the phone number (123) to collectthe funds. For example, the interchange (101) may determine the accountinformation (121) (e.g., an account identifier, such as a credit cardnumber, a bank account number, a debit card number, etc.) stored andassociated with the phone number (123) on the data storage facility(107) of the interchange (101) to charge the user using the accountinformation (121).

In one embodiment, in response to the payment request from the userterminal (111), the interchange (101) may send a notification message tothe mobile phone (117) at the phone number (123). The user is notrequired to provide a reply to complete the payment process. However,the user of the mobile phone (117) is provided with theoption/opportunity to reply and report a fraudulent use, or to cancelthe request (e.g., within a predetermined period of time).

In one embodiment, the data storage facility (107) stores a passwordassociated with the phone number (123) for authentication. In FIG. 27,after the interchange (101) receives (651) a password and a phone number(123) from a user terminal (111), the interchange (101) determines (652)whether the received password is the correct password for the phonenumber (123). If the received password is the correct password for thephone number (123), the interchange (101) associates (653) the userterminal (111) with the phone number (123) in the data storage facility(107). If, during the time period in which the user terminal (111) isassociated with the phone number (123), the interchange (101) receives(655) from the user terminal (111) a request to pay a payee (e.g., viathe user interface (201) illustrated in FIG. 8), the interchange (101)may approve (657) the request based on the confirmed association betweenthe user terminal (111) and the phone number (123) and pay the payeeusing funds associated with the phone number (123), without requiring aconfirmation via the mobile phone (117) at the phone number (123). Insome embodiments, after the user terminal (111) submits the phone number(123) to the interchange (101), the interchange (101) may request thepassword from the mobile phone (117) at the phone number (123).

In one embodiment, during the time period in which the user terminal(111) is associated with the phone number (123), the interchange (101)may automatically provide the phone number (123) in the text field (183)in the user interface (201) for submitting a payment request, asillustrated in the FIG. 8, based on the association between the userterminal (111) and the phone number (123). The phone number (123) can beprovided by the interchange (101) in the text field (183) as a defaultinput. Alternatively, the interchange (101) may not provide the phonenumber (123) and may require the user to enter the phone number (123) inthe text field (183) for enhanced security. In some embodiments, theinterchange (101) may dynamically determine whether or not to presentthe phone number (123) in the text field (183) based on a transactionpattern associated with the phone number (123). For example, if thecurrent request matches the pattern, the interchange (101) presents thephone number (123) as the default input to simplify user interactions;otherwise, the interchange (101) does not provide the phone number (123)in the text field (183) for enhanced security.

In FIG. 28, after the interchange (101) receives (661) a phone number(123) from a user terminal (111), the interchange (101) communicates(663) with the user for an advance approval for the user terminal (111)via a mobile phone (117) at the phone number (123). For example, theinterchange (101) may communicate with the mobile phone (117) at thephone number (123) for the advance approval and/or communicate with theuser terminal (111) to confirm a password associated with the phonenumber (123).

In one embodiment, the advance approval is specific for the userterminal (111); and the interchange (101) stores identifiers of the userterminal (111) with the advance approval. For example, the interchange(101) may communicate with the user terminal (111) and/or the mobilephone (117) to associate the user terminal (111) with the phone number(123) for the advance approval of one or more subsequent paymentrequests.

In some embodiments, the advance approval is not limited to a particularuser terminal (111). For example, the user may directly use the mobilephone (117) at the phone number (123) to communicate the advanceapproval to the interchange (101) without having to identify the userterminal (111). Alternatively, the user may use a particular userterminal (111) to initiate the communications with the interchange (101)for the advance approval without limiting the advance approval tosubsequent payment requests from the same particular user terminal(111).

In one embodiment, the advance approval is associated with the phonenumber (123) on the data storage facility (107). When a request to payvia the funds associated with the phone number (123) is received, theadvance approval associated with the phone number (123) is identifiedand applied by the interchange (101). The user does not have toexplicitly identify the advance approval in making the payment request.

In one embodiment, the interchange (101) may assign an identificationcode for the advance approval for enhanced security. The user may usethe identification code in the payment request to explicitly identifythe advance approval.

In one embodiment, the advance approval specifies a time limit for theexpiration of the approval, a budget amount for one or more paymentrequests, a limit on the types of permitted products and/or services, atime window for permissible payment requests, a frequency forpermissible payment requests, and one or more limits based on certaincharacteristics of the payees (e.g., web addresses, countries,categories).

In one embodiment, the advance approval may specify some limits on thepermissible user terminals (111). For example, the advance approval maylimit the advance approval to user terminals located with certaingeographic areas. The interchange (101) may determine the geographicareas of the user terminals (111) based on the IP addresses of the userterminals (111), the access points for wireless local areacommunications, the base stations for cellular communications, etc.

After the advanced approval is associated with the phone number (123),the interchange (101) may receive (665) from the user terminal (111) arequest to pay a payee via the phone number (123). Based on the advanceapproval the interchange (101) may approve (667) the request and pay(669) the payee using funds associated with the phone number (123),without requiring a confirmation message from the user viacommunications with the mobile phone (117) at the phone number (123).

In some embodiments, the interchange (101) may use the transactionhistory (127) to determine whether or not to require a confirmationmessage from the user via communications with the mobile phone (117) atthe phone number (123). The transaction history (127) may include anumber of records of prior confirmed/approved payment requests.

For example, based on the records of prior payment requests theinterchange (101) may determine a payment pattern for the phone number(123), such as a list of frequently used user terminals (111) for thephone number (123), a range for typical payment amounts, a time of daywithin which typical payment requests are received for the phone number(123), a list of frequently used payees paid via the phone number (123),a list of categories of services and/or products frequently paid for viathe phone number (123), a recent payment request confirmed within apredetermined period of time, etc.

In FIG. 29, the interchange (101) processes (671) a plurality ofrequests to pay via a phone number (123). The interchange (101)processes (671) the requests via communicating with the mobile phone(117) at the phone number (123). For example, the interchange (101) maysend a message to the mobile phone (117) at the phone number (123) andrequest a reply to the message from the mobile phone (117). For example,the interchange (101) may request a PIN from the mobile phone (117) atthe phone number (123) to confirm the requests. For example, theinterchange (101) may send one-time codes representing the requests tothe mobile phone (117) or receive one-time codes representing therequests from the mobile phone (117).

The interchange (101) stores (673) transaction records of the paymentrequests and determines (675) a pattern of the payment requests.

Subsequently, when the interchange (101) receives (677) from a userterminal (111) a request to pay a payee via the phone number (123), theinterchange (101) determines (678) whether the request matches thepattern. If the request matches the pattern, the interchange (101) pays(679) the payee using funds associated with the phone number (123),without requiring a confirmation communicated via the mobile phone (117)at the phone number (123) to speed up the payment process. Theinterchange (101) may send a notification to the mobile phone (117) atthe phone number (123), without requiring a reply prior to making thepayment.

In one embodiment, a personal digital assistant (PDA) is provided in aretail store to allow a merchant to initiate a payment request to theinterchange (101), which may also support transactions at other types ofretail terminals in other environments, such as automatic tellermachines (ATMs) in banks and point of sale (POS) terminals in retailstores.

In one embodiment, the PDA is a mobile device, which can be used notonly in a fixed-location retail system, but also in other locations. Forexample, agents may use the PDAs to take payments for door to door debtcollection, street sales, etc. The PDA can be configured to communicatewith the interchange (101) via a wireless communication connection(e.g., using a wireless wide area network, a wireless local areanetwork, or cellular telecommunications).

In one embodiment, when a customer is in a retail store, a cashier mayenter the phone number (123) of the customer into a retail terminal torequest a payment from the interchange (101) for the purchases made bythe customer. The customer gets a text message from the interchange(101) to confirm/authorize the payment request. If the customer respondsto the text message to confirm/authorize the payment request, theinterchange (101) makes a payment to the retailer using funds associatedwith the phone number (123) (e.g., funds collected via sending premiummessages to the mobile phone (117) at the phone number (123), or viacharging a credit or debit card associated with the phone number (123)using the account information (121)). Thus, the customer can leave theretail store with the purchased goods, just like after paying for thepurchased goods using a credit or debit card at the retail terminal.

In one embodiment, an ATM is configured to accept the phone number (123)entered by a customer to withdraw cash. The ATM transmits the phonenumber (123) in a request for funds to the interchange (101). Inresponse to the request, the interchange (101) sends a text message tothe mobile phone (117) at the phone number (123) to allow the user toconfirm or authorize the request. After the customer gets the textmessage on the mobile phone (117), the customer may reply to the textmessage to confirm/approve and then withdraw cash from the ATM. Theinterchange (101) provides to the bank of the ATM the correspondingfunds collected from the user.

In one embodiment, to speed up the transaction process at the retailterminal, the customer may send a pre-approval to the interchange (101)to authorize a subsequent transaction, such as a retail transaction oran ATM transaction, prior to reaching the retail terminal. Thus, tocheck out at the retail terminal, the customer just provides the phonenumber (123) to the retail terminal and does not have to wait for theconfirmation message from the interchange (101) and does not have toreply to the confirmation message to complete the transaction. After theretail terminal obtains the phone number (123) of the customer, theretail terminal can communicate with the interchange (101) to get fundsassociated with the phone number (123) to close the transaction, basedon the pre-approval.

FIGS. 30-33 show systems to facilitate retail transactions according tosome embodiments. In FIG. 30, the retail terminal (221) is configured toaccept the phone number (123) of the customer at a retail location. Insome embodiments, the customer may operate the retail terminal (221) andenter the phone number (123) to provide funds for a transaction, such aswithdrawing cash based on funds collected by the interchange (101). Insome embodiments, a retail agent may operate the retail terminal (221)and enter the phone number (123) to process a payment for a transaction,such as obtaining a payment for an order in a restaurant or for goods orservices purchased in a retail store.

In FIG. 30, after the retail terminal (221) obtains the phone number(123) for the transaction, the retail terminal (221) transmits a chargerequest (179) to the interchange (101) to charge the customer via thephone number (123). The interchange (101) communicates with the mobilephone (117) at the phone number (123) for the confirmation (173) of thecharge request.

In one embodiment, the interchange (101) communicates with the mobilephone (117) via text message to obtain the confirmation (173).Alternatively, or in combination, the interchange (101) may communicatewith the mobile phone (117) via multimedia messaging service (MMS),instant messaging, email, web requests and responses, WAP applications,etc.

After the customer confirms or approves the charge request (179) via themobile phone (117), the interchange (101) provides funds to the retailterminal (221) for the transaction.

For example, in FIG. 30, the interchange (101) may identify the accountinformation (121) stored and associated with the phone number (123) inthe data storage facility (107). The interchange (101) uses the accountinformation (121) to communicate with an account server (125) to charge(172) the user using the account information (121), which can be acredit card number, a debit card number, a checking account number, etc.

In one embodiment, the interchange (101) obtains the funds from theaccount of the user using the account information (121) and provides thefunds to allow the retail terminal (221) to perform the transaction. Forexample, the interchange (101) may provide the funds to the retaileroperating the retail terminal (221) to allow the retail terminal (221)to process a purchase made at the store of the retailer. For example,the interchange (101) may provide the funds to the bank of an ATM thatserves as the retail terminal (221); and thus the user can withdraw cashfrom the ATM.

In one embodiment, the retail terminal (221) is implemented withtraditional functions of retail terminals that are used at fixedlocations, such as a cash register. In other embodiments, the retailterminal (221) is implemented on a PDA with wireless communicationcapabilities, to allow payments to take place at various locations. Forexample, the PDA may be used for door to door debt collection, streetsales, etc.

In some embodiments, the retail terminal (221) is further configured toprovide an electronic receipt for the transaction completed at theretail terminal (221). For example, the retail terminal (221) mayprovide the electronic receipt to the interchange (101) for transmissionto the mobile phone (117) at the phone number (123). Alternatively, insome embodiments, the retail terminal (221) may be configured totransmit the electronic receipt to the mobile phone (117) via atelecommunication carrier, without providing the electronic receipt tothe interchange (101).

FIG. 30 illustrates an example in which the interchange (101) obtainsthe funds associated with the phone number (123) using the accountinformation (121) stored and associated with the phone number (123) inthe data storage facility (107). Alternatively, the interchange (101)may obtain the funds via the telecommunication carrier of the mobilephone (117) (without having to obtain and store the account information(121) from the user), as illustrated in FIG. 31.

In FIG. 31, the interchange (101) sends premium messages (225) to themobile phone (117) to obtain the funds as required by the charge request(179) to collect the funds for the transaction performed at the retailterminal (221).

In one embodiment, to reduce the time period the user waits for theretail terminal (221) to submit the charge request (179) and obtain aresponse from the interchange (101), the user of the mobile phone (117)may send a pre-approval (223) of an estimated amount that would berequested by the retail terminal (221). The mobile phone (117) sends thepre-approval (223) to the interchange (101), prior to the retailterminal (221) receiving the phone number (123), to allow theinterchange (101) to send the premium message (225) to the mobile phone(117) to collect the funds according to the estimated amount specifiedin the pre-approval (223). Thus, when the retail terminal (221)transmits the charge request (179) to the interchange (101), the processof transmitting the one or more premium messages (225) to the mobilephone (117) is completed, or partially completed. This reduces thewaiting period at the retail terminal (221).

In FIG. 31, the data storage facility (107) may be used by theinterchange (101) to store the balance (224) of the phone number (123)between the funds that have been collected from the mobile phone (117)and funds that have been applied to transactions (e.g., made at theretail terminal (221)). The interchange (101) may use the data storagefacility (107) to maintain records of charge requests (179) receivedfrom the retail terminal (221), premium messages (225) sent to themobile phone (117) at the phone number (123), and amount of fundsreceived from the telecommunication carrier of the mobile phone (117).

FIG. 32 illustrates an example of using a phone number (123) at an ATM(221) to withdraw cash. In FIG. 32, the ATM (221) is configured toreceive a phone number (123) (e.g., via a keypad or a touch screen ofthe ATM (221)). In response to the phone number (123) being received inthe ATM (221) to withdraw an amount of cash, the ATM (221) sends acharge request (179) to the interchange (101) to request a fundstransfer (227). In some embodiments, the ATM (221) sends the chargerequest (179) via the server (113) associated with the ATM (221).

In one embodiment, the interchange (101) communicates with the mobilephone (117) for a confirmation (173) of the charge request (179). If themobile phone (117) at the phone number (123) confirms the charge request(179), the interchange (101) provides funds to the server (113)associated with the ATM (221) via a funds transfer (227). The fundstransfer (227) provides the amount of funds for the cash withdrawal andfor any transaction fees the server (113) associated with the ATM (221)may charge.

In one embodiment, the user of the mobile phone (117) at the phonenumber (123) has an account (122) with the interchange (101). Theaccount (122) is associated with the phone number (123) stored in thedata storage facility (107). The user may provide funds to the account(122) via the mobile phone (117). The interchange (101) transfers fundsfrom the account (122) to the server (113).

In one embodiment, when the balance of the account (122) is notsufficient to provide the funds to satisfy the charge request (179), theinterchange (101) may communicate with the mobile phone (117) for aconfirmation to send one or more premium messages (225) to the mobilephone (117) to collect funds into the account (122).

In some embodiments, the mobile phone (117) may pre-authorize theinterchange (101) to collect the funds into the account (122) via thepremium messages (225). Thus, the user does not have to wait for theconfirmation (173) and the one or more premium messages (225) when usingthe ATM (221).

In some embodiments, the user may deposit funds into the ATM (221) andrequest the ATM (221) to transfer the deposited funds to the account(122) hosted on the data storage facility (107) of the interchange(101).

In some embodiments, the user may have an account with the bank of theATM (221) and the server (113). The ATM (221) is configured to receivethe requests from the user to transfer funds between the account (122)hosted on the data storage facility (107) of the interchange (101) andthe account with the bank of the ATM (221) and the server (113).

In some embodiments, the user does not have an account with the bank ofthe ATM (221) and the server (113). The ATM (221) is configured toaccess the account (122) hosted on the data storage facility (107) ofthe interchange (101), via funds transfer (227) between the server (113)and the interchange (101). For example, the ATM (221) may provide cashbased on funds transferred out of the account (122), or receive adeposit via funds transferred to the account (122).

FIG. 33 shows another example in which the ATM (221) uses theinterchange (101) to confirm a transaction performed at the ATM (221).In FIG. 33, the ATM (221) may receive a phone number (123) to identifyan account (122) stored on the server (113) associated with the ATM(221). Before operating on the account (122) (e.g., for cash withdrawal,for deposit, for funds transfer), the ATM (221) sends a request (229) tothe interchange (101) to request a confirmation (228). In response tothe request (229), the interchange (101) communicates with the mobilephone (117) to obtain a confirmation (173) for the transaction that isbeing processed at the ATM (221). After the interchange (101) obtainsthe confirmation (173) from the mobile phone (117), the interchange(101) sends a confirmation (228) as a response to the request (229). Theconfirmation (228) allows the ATM (221) to operate on the account (122).

In some embodiments, the ATM (221) may receive a different identifier(e.g., a banking card number) to identify the account (122). The server(113) identifies the phone number (123) to request a confirmation (228).

In some embodiments, the ATM (221) of a bank sends the request (229) andreceives the confirmation (228) via the server (113) of the bank.

FIG. 34 shows a user interface to pre-approve a transaction according toone embodiment. The user interface (190) as illustrated in FIG. 34 canbe used to generate a message (217) to provide the pre-approval (223) tocollect funds for a subsequent transaction. The message (217) mayidentify an estimated amount for the next transaction, the estimatedtime for the transaction, and an indication of the location of thetransaction.

In one embodiment, the user interface (190) is implemented on a mobilephone (117) at the phone number (123). The mobile phone (117) isconfigured to determine its location (e.g., via a Global PositioningSystem (GPS), or a positioning system based on a cellulartelecommunication network). The user may indicate the authorized retailterminals by providing the current location of the mobile phone (117)while the mobile phone (117) is located near the authorized retailterminals. In one embodiment, the interchange (101) can compare thelocation of the retail terminal (221) and the location provided in theauthorization message (217) to determine whether the charge request(179) should be rejected or accepted. For example, the user may providethe pre-approval (223) before beginning to shop in a retail store, orbefore a meal is served in a restaurant, so that the time required forprocessing the payment can be reduced.

Alternatively, the mobile phone (117) may use other identificationinformation, such as the phone number of the retailer, the name of theretailer, etc., to provide pre-authorization for anticipatedtransactions at the retail terminal (221), in addition to, or incombination with, the location information illustrated in FIG. 34.

FIG. 35 shows a user interface to confirm an automatic teller machine(ATM) transaction according to one embodiment. In FIG. 35, the userinterface (190) is used to present a message (217) from the interchange(101) to confirm a transaction at an ATM (221). The message identifiesthe ATM (e.g., via the location, bank affiliation, etc.).

In FIG. 35, the message (217) presents a number of options to allow theuser to select a source of funds for the request to withdraw cash. Forexample, the interchange (101) may collect the funds via premium SMSmessages (e.g., option “1” in FIG. 35), or charge a credit card on filewith the interchange (101) (e.g., option “2” in FIG. 35) to provide thefunds for the cash request at the ATM (221) identified in the message(217).

In some embodiments, the message (217) may further request a password ora PIN to authenticate the user of the mobile phone (117) on which theuser interface (190) is presented.

FIG. 36 shows a method performed on a retail terminal according to oneembodiment. In FIG. 36, a retail terminal (221) is configured to receive(571) a phone number (123) of a customer. The retail terminal (221)transmits (573) the phone number (123) to an interchange (101) torequest funds from the customer for a transaction requested by thecustomer. After the funds are received (575) from the interchange (101),the retail terminal (221) performs (577) the transaction requested bythe customer.

FIG. 37 shows a method to facilitate a retail transaction according toone embodiment. In FIG. 37, a mobile phone (117) at a phone number (123)transmits (551) a pre-approval to an interchange (101). Based on thepre-approval, the interchange (101) may prepare funds for an anticipatedtransaction. For example, the interchange (101) may transmit one or morepremium messages to the mobile phone (117) to collect the funds for theanticipated transaction into the account (122) hosted on the datastorage facility (107) of the interchange (101).

In FIG. 37, after the phone number (123) is provided (553) to a retailterminal (221) for a transaction on the retail terminal (221), theretail terminal transmits (555) to the interchange (101) the phonenumber (123) with a request (179) for funds. The interchange (101)correlates (557) the pre-approval (223) with the request (179), andapproves (559) the request based on the pre-approval (223), and provides(561) funds associated with the phone number (123) for the transaction.The interchange (101) transmits a message to the retail terminal toallow the retail terminal (563) to perform the transaction.

In one embodiment, the retail terminal (221) is a point of sale (POS)terminal. In one embodiment, the retail terminal (221) is implementedvia a personal digital assistant (PDA).

In one embodiment, the retail terminal (221) is positioned in a retailstore for checkouts; and the mobile phone (117) is used to communicatewith a server computer (e.g., interchange (101)) to confirm thetransaction, prior to the retail terminal (221) receiving the phonenumber (123) of the customer.

In one embodiment, the retail terminal (221) is a mobile device adaptedto perform transactions at different locations.

In one embodiment, the transaction is confirmed via a message sent fromthe mobile phone (117) as a response to a message sent from the servercomputer (e.g., interchange (101)) to the mobile phone (117).

In one embodiment, the retail terminal (221) is an automatic tellermachine (ATM) (221); and the transaction at the ATM (221) includesproviding the funds to the customer in cash.

In one embodiment, the server computer (e.g., the interchange (101)) isto transmit a first message to the mobile phone (117) at the phonenumber (123) to request a confirmation of withdrawing the funds from theATM (221); and the server computer (e.g., the interchange (101))provides the funds to a bank of the ATM (221) after the server computerreceives a confirmation reply to the first message. In one embodiment,the customer has no bank account with the bank.

In one embodiment, the mobile phone (117) is used to communicate withthe server computer (e.g., interchange (101)) to confirm the transactionvia pre-approving the transaction prior to the providing of phone number(123) to the retail terminal. The server computer is to transmit themessage indicating that the funds are available for the transaction, inresponse to a determination that a pre-approved amount matches an amountof the transaction. In one embodiment, the server computer (e.g.,interchange (101)) is to transmit the one or more premium messages (225)to collect the funds for the anticipated transaction, prior to theretail terminal (221) receiving the phone number (123) of the customer.

In one embodiment, the server computer is to transmit the messagefurther in response to a determination that a location of the retailterminal (221) matches a location of the mobile phone (117) where themobile phone (117) pre-approves the transaction.

In one embodiment, the mobile phone (117) pre-approves the transactionby transmitting to the server computer (e.g., interchange (101)) amessage indicating an allowable amount for the transaction and anidentity of the retail terminal (221). The identity of the retailterminal (221) may include a phone number of a merchant operating theretail terminal (221).

In one embodiment, the retail terminal (221) is configured to provide anelectronic receipt to the mobile phone (117) via the server computer(e.g., interchange (101)).

In one embodiment, the server computer (e.g., interchange (101)) is tocommunicate with the mobile phone (117) to confirm the transaction viashort message service (SMS), email, instant messaging, multimediamessaging service (MMS), etc. The confirmation may include theelectronic receipt received from the retail terminal (221).

In one embodiment, the interchange (101) is configured to allow a userto provide a cell phone number (123) to pay for goods or services, usinga user account tied to the cell phone number (123) of the user.

For example, the user can enter the cell phone number (123) into a POSterminal, an online checkout system, a mobile application, or a paymentor purchase process system, device, service, or application to pay forgoods or services.

In one embodiment, the account is hosted on the interchange (101), whichcan provide Internet-based services via at least communicating overInternet. The user account may store the identity of the user andlogin/authentication information. The interchange (101) may charge tothe mobile phone bill to fund the account and/or make payments. The useraccount may further store financial card information, such as a creditcard, a pre-paid card, a debit card, etc. The user account may be linkedto one or more bank accounts of the user, such as a checking account ora savings account. The user account may be linked to other financialaccounts, such as an investment account, a payment intermediary account,etc. The user account hosted on the interchange (101) is configured tostore values or credits for the user, such as credits from refunds frommerchant, credits/funds added by the user to the account via charginglinked accounts, such as bank accounts, credit accounts, or via userdeposit.

In one embodiment, the interchange (101) is configured to performmultiple-factor authentication when making payments using the useraccount. For example, the user may be requested to reply by text messagefrom the mobile phone (117) having the phone number (123) for theconfirmation of the payment request, and/or provide a PIN, a one-timerandom PIN, a password, or answers to security questions (e.g., using amobile application running on the mobile phone (117)) to pass theauthentication operation. In some embodiments, the user is requested toprovide the PIN or password at the time of entering the phone number(123) to make the payment request.

In one embodiment, the mobile phone (117) is configured to receiveinput, such as PIN, password, one-time code, reply message, etc., viavoice recognition, keyboard input, and/or touch screen input (e.g.,through handwriting recognition, or on-screen keyboard).

FIG. 38 shows an account according to one embodiment. In FIG. 38, thephone number (123) is used to identify the account (122) hosted on thedata storage facility (107) of the interchange (101). The user can usethe phone number (123) to access the services associated with theaccount (122).

In one embodiment, the phone number (123) is associated with theidentification of the mobile carrier (605) to allow the user to fund theaccount (122) via the mobile phone bill from the mobile carrier (605).

For example, a premium message can be sent from the interchange (101) tothe phone number (123) to obtain an amount of funds from the mobilecarrier (605), via the mobile phone bill, according to a predeterminedprice associated with the premium message.

For example, the user may be instructed to send a premium message fromthe phone number (123) to the interchange (101) to provide an amount offunds according to a predetermined price associated with the premiummessage.

For example, the interchange (101) may send a message to the mobilecarrier (605) to request the mobile carrier to bill an amount to themobile phone bill of the phone number (123) and obtain funds fordepositing in the account (122) or paying a merchant (or other types ofpayees, such as a family member, a friend, a relative, a charity, etc.)

In one embodiment, the data storage facility (107) is further configuredto store account information (121), such as data that identifies variousfinancial accounts of the user, such as checking account (611), savingsaccount (613), investment account (621), credit card account (615),debit card account (617), prepaid card account (619), and/or paymentintermediary account (607) (e.g., third party payment services thatidentify users via their email addresses, or other identifiers).

In one embodiment, the account information (121) also includes dataidentifying online accounts (609) hosted on servers (113) that providevarious services and/or products to the user. The servers (113) maycharge the user for accessing premium services and/or products and/orfor subscription. In some embodiments, the servers (113) may maintainaccount balances for the respective online accounts (609) for thecredits/values that the user has purchased (e.g., purchased using theaccount (122) as a payment instrument).

In one embodiment, the interchange (101) allows the user to maketransfers between various accounts, such as the account (122) hosted onthe interchange (101), the online account (609) hosted on a third partyserver (113) and/or other types of financial accounts, such as checkingaccount (611), savings account (613), investment account (621), creditcard account (615), debit card account (617), prepaid card account(619), and/or payment intermediary account (607).

In one embodiment, the interchange (101) performs authentication for theservers (113) and thus allows the user to sign in the servers using thephone number (123) and the mobile phone (117) having the phone number(123), as discussed in connection with FIGS. 20-25.

In one embodiment, the data storage facility stores a balance (224),identity data (601) and security data (603) for the account (122). Thebalance (224) represents the funds/credits stored in the account (122).The identity data (601) identifies the user. The security data (603) isused for the authentication of the user.

For example, the security data (603) may include a password or PIN foraccessing the account (122), a one-time code assigned to a particularpayment request, a seed for one-time passwords to authenticate themobile phone (117) at the phone number (123), etc.

In one embodiment, the interchange (101) is configured to authenticatethe user using the security data (603), in ways discussed in connectionwith FIGS. 15-19. For example, the interchange (101) may authenticatethe user to allow the user to access the linked online account (609)hosted on the server (113), or to process a payment request (or toperform a fund transfer between two of the accounts (122, 611, 613, 615,617, 619, 607, 609, 621).

For example, the interchange (101) may authenticate a request associatedwith the phone number (123) via communicating with the mobile phone(117) at phone number (123) to verify that the requester is inpossession of the mobile phone (117) and via a further security measure,such as a password, a PIN, a one-time code, a one-time password, etc.

For example, the user may select a password or a PIN that is stored inthe account (122) as part of the security data (603). When the usermakes a request at a user terminal (111) by identifying the phone number(123), the interchange (101) may authenticate the user via requestingthe password or PIN from the user terminal (111), or from the mobilephone (117) at the phone number (123).

For example, to authenticate a request made at a user terminal (111),the interchange (101) may assign a one-time code to the request,transmit the one-time code to the user via the mobile phone (117) andrequest the one-time code at the user terminal (111) for verification.Alternatively, the interchange (101) may assign a one-time code to therequest, transmit the one-time code to the user via the user terminal(111) and request the one-time code from the mobile phone (117) forverification.

For example, to authenticate the mobile phone (117), the interchange(101) may request a one-time password generated on the mobile phone(117) (or generated on a separate device assigned to the user). In oneembodiment, access to the one-time password generator (361) is passwordprotected for enhanced security.

In one embodiment, multiple security measures are used together forcertain requests, such as when the amount of a request is above athreshold or, when an accumulated transaction amount within apredetermined period of time is above a threshold. For example, accessto certain accounts (e.g., online account (609)) may require lesssecurity measures; and access to some other accounts (e.g., bankaccounts (e.g., 611, 613, or 621)) may require more security measures.

In one embodiment, the user can use the phone number (123) at variouspayment terminals to pay for goods or services, as illustrated in anddiscussed in connection with FIGS. 30-37.

For example, in one embodiment, the user may enter the phone number(123) in a point of sale (POS) terminal in a retail store to pay forgoods and services. The POS terminal may be configured to processfinancial cards, such as credit cards, prepaid cards, debit cards, etc.In one embodiment, the POS terminal is further configured to processphone numbers. For example, the user may select a payment optionassociated with the interchange (101) and key in the phone number (123)on the POS terminal. Alternatively, the POS terminal can be configuredto communicate with the mobile phone (117) in an automated way to obtainthe phone number (123), via radio frequency identification (RFID), nearfield communication (NFC), Bluetooth discovery, etc.

After the use confirms the user of the phone number (123) to make apayment on the POS terminal, the POS terminal is configured tocommunicate with the interchange (101) to request a payment using theaccount (122) associated with the phone number (123). To authenticatethe request from the POS terminal, the interchange (101) communicateswith the mobile phone (117) at the phone number (123) to request aconfirmation. One or more additional security measures, such as PIN,password, one-time code, and one-time password, can be used to furtherauthenticate the request. In some embodiments, the user maypre-authorize the payment request (e.g., while waiting in the line tocheckout, as discussed in connection with FIGS. 26-29).

In one embodiment, the phone number (123) can be entered into an ATMmachine to request cash backed by funds from the account (122), or tomake a deposit to the account (122). For example, the user may key inthe phone number (123) to request a transaction in the account (122).Alternatively, the mobile phone (117) may be configured to provide thephone number (123) automatically to the ATM, via RFID, NFC, orBluetooth. The interchange (101) is configured to transfer money to orfrom the bank or the owner of the ATM to facilitate the cash withdrawal,or to accept a deposit.

In one embodiment, the phone number (123) can be used on a mobileapplication (e.g., running on the mobile phone (117) having the phonenumber (123)) to pay for premium accesses and/or subscription and/or topurchase credits/points for consumption within the mobile application.

In one embodiment, the phone number (123) supported by the interchange(101) can be used as a payment option in an online checkout system, suchas an online shopping cart checkout system. The checkout system isconfigured to communicate with the interchange (101) to obtain thepayment from the account (122) identified by the phone number (123) onbehalf of the merchant.

In some embodiments, the interchange (101) may also use the accountinformation (121) to make payments on behalf of the user, withoutpulling the funds through the account (122). For example, after apayment request is authenticated, the interchange (101) may provide someof the account information (121) to the merchant (e.g., via POSterminal, ATM, retail terminal, online checkout system, etc.) to chargethe corresponding account for the payment. Alternatively, to avoidgiving out the account information (121) to merchants, the interchange(101) may instruct the financial institutions of the correspondingaccounts to make the payment to the merchant.

In some embodiments, the interchange (101) may also use the accounts(e.g., 122, 611-621 and 607) to pay the phone bill for the phone numberfrom the mobile carrier (605).

In one embodiment, the phone number (123) as supported by theinterchange (101) is used by the user as a central hub to access variousfinancial accounts linked to the phone number (123). The details ofhandling the different types of accounts can be shielded from the uservia a unified user interface provided by the interchange (101).

FIG. 39 shows a method to make payments to one embodiment. In FIG. 39,the data storage facility (107) of the interchange (101) is configuredto store (631) data to associate a phone number (123) with an account(122). The interchange (101) is configured to fund (633) the accountusing a phone bill of the phone number (123) and a plurality of fundingsources (e.g., accounts 607 and 611-621) associated with the account(122). The interchange (101) is configured to receive (635) from paymentterminals (e.g., 111, 221) requests to pay via the phone number (123).The interchange (101) is configured to authenticate (637) the requestsvia security data (603) associated with the account (122) and viacommunications with a mobile phone (117) having the phone number (123).The interchange (101) is configured to effect (639) payments using theaccount (122) in accordance with the requests after the requests areauthenticated.

In one embodiment, the security data (603) includes a password, apersonal identification number (PIN), a one-time code, a seed for thegeneration of one-time passwords, answers to security questions, etc.

In one embodiment, the interchange (101) is configured to request thepassword or the PIN from the payment terminals respectively toauthenticate (637) the requests (e.g., prior to the communication withthe mobile phone (117)). Alternatively, the interchange (101) can beconfigured to request the password or the PIN from the mobile phone(117) having the phone number (123) to authenticate (637) the requests,or to receive one-time passwords from an application running on themobile phone (117) to authenticate (637) the requests.

In one embodiment, the security data (603) includes answers to securityquestions; and the account (122) further stores identity data (601) ofthe user, such as social security numbers, date of birth, voicecharacteristics, finger print data, etc., which can be used toauthenticate the user via the mobile phone (117). For example, themobile phone (117) may include a mobile application to extract voicecharacteristics from a voice input to construct a text message for theconfirmation of a request related to the account (122); and theinterchange (101) is configured to compare the received voicecharacteristics and the corresponding stored voice characteristics toauthenticate the user. For example, the mobile phone (117) may be usedto scan a finger print of the user to allow the interchange (101) toauthenticate the user.

In one embodiment, the security data (603) includes voicecharacteristics of the user; and to authenticate requests theinterchange (101) is to receive a voice input from the mobile phone(117) and match the voice input with the voice characteristics of theuser. In some embodiments, the interchange (101) performs voicerecognition from the voice input. In another embodiment, a mobileapplication running on the mobile phone (117) is used to perform thevoice recognition operation to allow the user to compose a text message;and the interchange (101) is configured to receive the text message fromthe mobile phone (117) for the confirmation of the correspondingrequest. In some embodiments, the mobile application may communicatewith a third party server in performing the voice recognition operation.

In one embodiment, the security data (603) includes one-time codes; andto authenticate the request, the interchange (101) is configured togenerate the one-time codes in response to the requests, to provide theone-time codes to the payment terminals respectively for the requests,and to communicate with the mobile phone (117) having the phone number(123) to obtain the one-time codes back for authentication.

In another embodiment, the security data (603) includes one-time codes;and to authenticate the request, the interchange (101) is configured togenerate the one-time codes in response to the requests, to communicatethe one-time codes to the mobile phone (117) having the phone number(123), and to request the one-time codes back from the payment terminalsrespectively to authenticate the requests.

In one embodiment, to authenticate (637) the requests the interchange(101) is configured to receive confirmation messages from the mobilephone (117) having the phone number (123); and confirmation messagesinclude references to the requests respectively. In one embodiment, theconfirmation messages are composed on the mobile phone (117) as a replyto messages from the interchange (101); and the user may provide inputto the confirmation message via voice input to the mobile phone (117),or via keyboard or touch screen input.

In one embodiment, the interchange (101) is configured to add funds tothe account (122) in response to credits to the phone number (123) frommerchants. For example, when the user requests refunds, or a rebate froma merchant, the user may provide the phone number (123) to allow themerchant to fund the account (122) hosted on the interchange (101).

In one embodiment, at least one payment of the payments is performed viainstructing a respective merchant to charge one of the funding sourcesfor the payment.

In one embodiment, at least one payment of the payments is performed viainstructing one of the funding sources to make the payment to arespective merchant.

In one embodiment, the payment terminals include a point of saleterminal, an online checkout system, a purchase processing system of anonline merchant, an online application to charge a premium for servicesof the application, and/or a payment intermediary service.

In one embodiment, the interchange (101) stores identificationinformation of the plurality of funding sources (e.g., accounts 611-621and 607). For example, one payment intermediary account may beidentified via an email address of the user. In one embodiment, theplurality of funding sources may include one or more of: a checkingaccount (611), a savings account (613), an investment account (621), acredit card account (615), a debit card account (617), a prepaid cardaccount (619), and a payment intermediary account (607).

In one embodiment, a system and method are configured to set up, store,retrieve and authorize a financial payment transaction, where an accountidentification number, such as a credit card number, a bank card number,or a primary account number, is received and translated into a mobilephone number (e.g., a Mobile Station International Subscriber DirectoryNumber (MSISDN)) as a primary account number for payment processing.

In one embodiment, the interchange (101) uses the data storage facility(107) to securely store one or many account identification numberslinked to a mobile phone number (123) for a specific user. In oneembodiment, account information (121) identifying one or more financialaccounts is linked to the mobile phone number (123), as illustrated inFIG. 38. The account information (121) and/or the mobile phone number(123) provide access to a plurality of funding sources and/or methods,such as mobile billing, stored value, credit, payment card, bankaccount, Automated Clearing House (ACH), debit, pre-paid, gift card,etc.

In one embodiment, the interchange (101) is configured to accept astandard credit authorization request using a credit card number from amerchant or merchant acquiring entity. The interchange (101) is to lookup the mobile phone number (123) corresponding to the credit card numberand process the payment using the mobile phone number (123). Thestorage, encryption, and decryption of the account information (121)allows typical credit card processing systems to interact with theinterchange (101) for processing payments. Thus, a user can use a creditcard at a point of sales (POS) terminal to actually make a mobile phonebased billing transaction, or any other type of payment means tied tothe mobile phone number (123).

FIGS. 40-42 illustrate systems to make mobile phone based payments usingaccount identifiers according to some embodiments.

In FIG. 40, the account information (121) includes an account numberstored in the card (701), such as a credit card, a debit card, a prepaidcard, a banking card, etc. In the data storage facility (107), theaccount information (121) is linked to the phone number (123) of themobile phone (117).

In one embodiment, when the card reader (703) obtains the account numberfrom the card (701) for a payment transaction, the card reader (703)transmits the charge request (179) to the interchange (101). Theinterchange (101) uses the data associating the phone number (123) andthe account information (121) to determine the phone number (123)associated with the account number of the card (701).

In one embodiment, in response to the charge request (179) thatidentifies the account number of the card (701), the interchange (101)communicates with the mobile phone (117) at the phone number (123) thatis linked to the account number of the card (701) in the data storagefacility (107) to confirm (173) the transaction.

In one embodiment, after the confirmation (173) of the transaction, theinterchange (101) transmits one or more premium messages (225) to themobile phone (117) to collect funds for the payment. Alternatively or incombination, the interchange (101) is configured to make the paymentresponsive to the charge request (179) using the stored value account(122), or another account identified by the account information (121)associated with the phone number (123).

In one embodiment, the interchange (101) is configured as one of thestandard components in a payment processing network, such as a POSterminal, an issuer processor, an acquirer processor, a payment cardprocessor, or in communication with one of the standard components inthe payment processing network. Thus, the interchange (101) is toreceive charge request (179) from the payment processing network.

For example, in one embodiment, the interchange (101) is configured asan issuer of the account number carried in the card (701). Thus, thecard reader (703) at a POS terminal of a merchant can communicate thecharge request (179) to the interchange (101) via a standardized paymentnetwork; and the infrastructure of the standardized payment network canbe used to receive the charge request (179) without modification.

For example, in one embodiment, the interchange (101) is configured tocommunicate with an issuer processor of the card (701). When the issuerprocessor receives the authorization request associated with the accountnumber of the card (701), the issuer processor forwards theauthorization request to the interchange (101) for the confirmation(173). When the issuer processor settles the authorized transaction forthe card (701), the issuer processor is to communicate with theinterchange (101) to obtain funds associated with the phone number(123). In one embodiment, the issuer bank and the interchange (101)provide the card (701) as a co-branded card.

In one embodiment, the issuer processor is part of the interchange(101). In another embodiment, the issuer processor is distinct andseparate from the interchange (101).

In one embodiment, the POS terminal associated with the card reader(703) is configured to determine that the card (701) is associated withthe interchange (101) (e.g., based on the bank identification portion ofthe account number of the card (701)), and route the charge request(179) directly to the interchange (101) without going through a paymentnetwork for processing credit cards.

In one embodiment, the interchange (101) is configured to receive thecharge request (179) from an acquirer processor of the merchantoperating the POS terminal associated with the card reader (703). In oneembodiment, the interchange (101) is configured as an acquirer processorof the merchant operating the POS terminal associated with the cardreader (703) to receive the charge request (179).

In one embodiment, the interchange (101) is configured to receive thecharge request (179) from a payment card processor, such as Visa,MasterCard, American Express, Discover, etc.

In one embodiment, the charge request (179) represents a combinedauthorization and settlement request. An authorization request and asettlement request are transmitted separately from the POS terminalassociated with the card reader (703) to the interchange (101) for eachpayment transaction.

In one embodiment, the interchange (101) is configured to perform theconfirmation (173) with the mobile phone (117) in response to theauthorization request and to transmit the premium message (225) inresponse to the settlement request.

In one embodiment, the account (122) is a card account identified by theaccount number of the card (701). For example, in one embodiment, theaccount (122) is a credit card account represented by the card (701)when the card (701) is a credit card. For example, in one embodiment,the account (122) is a debit card account represented by the card (701)when the card (701) is a debit card. For example, in one embodiment, theaccount (122) is a prepaid account represented by the card (701) whenthe card (701) is a prepaid account card. In some embodiments, theaccount (122) is a checking account or savings account represented bythe card (701).

In one embodiment, the account (122) is a stored value accountrepresented by the phone number (123) but not directly represented bythe card (701).

In one embodiment, the card (701) includes a magnetic strip attached toa plastic card. The magnetic strip stores the account number of the card(701); and the card reader (703) is configured to read the accountnumber from the magnetic strip.

In one embodiment, the card (701) includes a radio frequencyidentification (RFID) tag that provides the account number of the card(701) to the card reader (703) without physically contacting the cardreader (703).

In one embodiment, the card (701) includes a near field communication(NFC) device to provide the account number to the card reader (703).

In one embodiment, the card (701) is implemented as a smart cardintegrated in a mobile device, such as the mobile phone (117). When theaccount number of the card (701) is obtained via an authorized cardreader (703) from the card (701) embedded in the mobile phone (117) viaa secure communication channel, such as near field communication (NFC),the interchange (101) may skip the confirmation (173) with the mobilephone (117).

In FIG. 41, the interchange (101) is configured to receive the chargerequest (179) from the card reader (703) prior to the server (113) ofthe issuer of the card (701) receiving an authorization and/orsettlement request corresponding to the charge request (179). The card(701) carries the account number (707), which is obtained by the cardreader (703) and transmitted to the interchange (101) with the chargerequest (179). In response to the charge request (179), the interchange(101) is to communicate with the mobile phone (117) for the confirmation(173) of the charge request (179). After the confirmation (173) of thecharge request (179), the interchange (101) is to communicate with theserver (113) hosting the account having the account number (707) forauthorization (705).

In another embodiment, the interchange (101) is configured tocommunicate with the server (113) for the authorization (705) of thecharge request (179). After the authorization (705) of the chargerequest (179), the interchange (101) is to further communicate with themobile phone (117) for the confirmation (173).

In a further embodiment, the interchange (101) is configured tocommunicate with the server (113) for the authorization (705) andcommunicate with the mobile phone (117) for the confirmation (173) inparallel. The interchange (101) is to determine whether or not toapprove the charge request (179) based on the result of theauthorization (705) with the server (113) and the result of theconfirmation (173) with the mobile phone (117). For example, in oneembodiment, the interchange (101) is to approve the charge request (179)when one of the authorization (705) and the confirmation (173) issuccessful; and in another embodiment, the interchange (101) is toreject the charge request (179) when one of the authorization (705) andthe confirmation (173) is not successful.

In one embodiment, when the interchange (101) approves the chargerequest (179), the interchange (101) charges the user and pays themerchant operating the card reader (703) using funds associated with thephone number (123) that is linked to the account number (707) in thedata storage facility (107) of the interchange (101). In one embodiment,the funds associated with the phone number (123) have a plurality ofsources, as discussed in connection with FIG. 38.

FIG. 42 illustrates an embodiment in which the interchange (101) isconfigured to charge an account having an account number (713) differentfrom the account number (711) stored in the card (701).

In FIG. 42, the data storage facility (107) stores account information(121) that includes both the account numbers (711 and 713). The accountinformation (121) is linked to the phone number (123) of the mobilephone (117) in the data storage facility (107). In one embodiment, theaccount information (121) further stores user configurable rules on howto select funding sources for charge requests.

For example, in one embodiment, the user may specify to use funds fromthe account number (711) for certain categories of charges, for chargesmade during certain time periods, and/or for purchases made with certainmerchants in certain geographical areas. In one embodiment, some of theuser specified preferences are based on the balances of the accountsidentified by the account numbers (e.g., 711, 713). In one embodiment,some of the user specified preferences are based on the amounts to bepaid for the respective charge request (e.g., 179). In one embodiment,the interchange (101) is programmed with one or more rules for theselection of the funding sources that may or may not be modifiable bythe user.

In one embodiment, when the charge request (179) identifying the accountnumber (711) is received from the card reader (703), the interchange(101) is to use the account information (121), user preferences and/orsystem rules to select a funding source of the phone number (123), suchas the account having the account number (713) that is different fromthe account number (711) of the card.

In one embodiment, after the confirmation with the mobile phone (117),the interchange (101) is to communicate with the server (113) that hoststhe account having the account number (713) to charge (709) the user.

In one embodiment, the interchange (101) uses the account hosts on theserver (113) to replenish the stored value account (122) when the storedvalue account (122) has a balance below a threshold, or when the balanceof the account is not sufficient to fulfill the charge request (179).When the account (122) has a sufficient balance, the interchange (101)is to use the account (122) to fulfill the charge request (179).

In one embodiment, the interchange (101) may also obtain the funds toreplenish the account (122) via the communication carrier of the mobilephone (117). For example, in one embodiment, the interchange (101) is totransmit premium messages to the mobile phone (117) to collect funds toreplenish the stored value account (122). In another embodiment, theinterchange (101) is to request premium messages from the mobile phone(117) to collect funds to replenish the stored value account (122). In afurther embodiment, the interchange (101) is to obtain the funds throughthe communication carrier via operator billing.

FIG. 43 shows a method to make payments via account identifiersaccording to one embodiment. In FIG. 43, the method includes storing(731) in the data storage facility (107) account data (e.g., 121, 123)to associate a phone number (123) and an account identification number(e.g., 707, 711), receiving (733) in a common format processor (133) apayment request (e.g., 179) identifying the account identificationnumber (e.g., 707, 711), determining (735) by the common formatprocessor the phone number (123) based on the account data (e.g., 121,123) and the account identification number (e.g., 707, 711), and making(737) a payment responsive to the payment request (e.g., 179) usingfunds associated with the phone number (123). In one embodiment, thefunds are from a credit account, a debit account, a prepaid account, achecking account, a savings account, a payment intermediary account, astored value account uniquely identified by the phone number (123), agift card account, or a phone bill or the account of the phone number(123) with a telecommunication carrier (e.g., charged via premium shortmessage service messages transmitted to the phone number (123)).

In one embodiment, the account identification number (e.g., 707, 711) isissued by a bank to a user of the card (701) that carries the accountidentification number (e.g., 707, 711). The account identificationnumber (e.g., 707, 711) represents an account of the user at the bank.In one embodiment, the account of the user represented by the accountidentification number (e.g., 707, 711) is hosted on the server (113) ofthe bank.

In one embodiment, the funds used to make (737) the payment are from afunding source different from the account at the bank identified by theaccount identification number (e.g., 707, 711).

In one embodiment, the payment request (e.g., 179) is received from thebank of the account identified by the account identification number(e.g., 707, 711), such as a credit account, a debit account, a prepaidaccount, a checking account, a savings account, a stored value account,a gift card account.

In one embodiment, the interchange (101) is configured to communicatewith the mobile phone (117) at the phone number (123) to confirm (173)the payment request. For example, the interchange (101) may transmit atext message to and/or receive a text message from the mobile phone(117) at the phone number (123) to confirm (173) the payment request(e.g., 179) and/or the account identification number (e.g., 707, 711).In one embodiment, the confirmation (173) is performed via communicatingwith a mobile application running on the mobile phone (117) at the phonenumber (123), pushing a notification to the mobile phone (117) at thephone number (123), and/or communicating with the mobile phone (117) viaa mobile interface.

In one embodiment, the interchange (101) is configured to communicatewith the bank, a payment network, or a merchant acquirer forauthorization of a transaction in an amount according to the paymentrequest (179), and then communicate with the mobile phone (117) for theconfirmation (173) in response to an authorization approval of thetransaction. In one embodiment, the interchange (101) is configured toobtain the approval without subsequently requesting settlement of thetransaction. The authorization (705) communication improves the securityof using the funds associated with the phone number (123).

In one embodiment, the common format processor (133) determines a set ofone or more premium messages based on an amount of the payment request(179) and uses one of the converters (131) corresponding to thecontroller (115) of the mobile phone (117) at the phone number (123) totransmit the set of one or more premium message to the mobile phone(117) at the phone number (123). The set of one or more premium messagescauses the telecommunications carrier to charge the mobile phone (117)and collect funds for the interchange (101).

In one embodiment, the payment request (179) is received from a point ofsales (POS) terminal having the card reader (703), or other devices thatare configured to receive the account identification number (e.g., 707,711) from the card (701) and/or authenticate the card (701). In oneembodiment, the POS terminal is configured to communicate with a mobiledevice (e.g., the card (701)) via near field communication (NFC) toobtain the account identification number (e.g., 707, 711). In oneembodiment, the mobile device includes the mobile phone (117). In oneembodiment, the payment request is received via an internet connecteddevice or a mobile connected device, such as web browsers, personalcomputers, tablet computers, notebook computers, mobile phones,televisions, etc.

In one embodiment, the account identification number (e.g., 707, 711)received in the payment request is used to identify a funding source forthe payment; and the funding source is represented by a phone number orother identifiers, such as an email address, another bank card number,an account number, a login for a social networking website, etc.

FIG. 44 shows a data processing system, which can be used in variousembodiments. While FIG. 44 illustrates various components of a computersystem, it is not intended to represent any particular architecture ormanner of interconnecting the components. Some embodiments may use othersystems that have fewer or more components than those shown in FIG. 44.

In one embodiment, each of the interchange (101), the data storagefacility (107), the controllers (115), the mobile phones (117), the userterminals (111), the account server (125) and the servers (113) can beimplemented as a data processing system, with fewer or more components,as illustrated in FIG. 44.

In FIG. 44, the data processing system (401) includes an inter-connect(402) (e.g., bus and system core logic), which interconnects amicroprocessor(s) (403) and memory (408). The microprocessor (403) iscoupled to cache memory (404) in the example of FIG. 44.

The inter-connect (402) interconnects the microprocessor(s) (403) andthe memory (408) together and also interconnects them to a displaycontroller, display device (407), and to peripheral devices such asinput/output (I/O) devices (405) through an input/output controller(s)(406).

Typical I/O devices include mice, keyboards, modems, network interfaces,printers, scanners, video cameras and other devices which are well knownin the art. In some embodiments, when the data processing system is aserver system, some of the I/O devices, such as printer, scanner, mice,and/or keyboards, are optional.

The inter-connect (402) may include one or more buses connected to oneanother through various bridges, controllers and/or adapters. In oneembodiment, the I/O controller (406) includes a USB (Universal SerialBus) adapter for controlling USB peripherals, and/or an IEEE-1394 busadapter for controlling IEEE-1394 peripherals.

The memory (408) may include ROM (Read Only Memory), volatile RAM(Random Access Memory), and non-volatile memory, such as hard drive,flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. Non-volatile memory is typically a magnetic hard drive, amagnetic optical drive, an optical drive (e.g., a DVD RAM), or othertype of memory system which maintains data even after power is removedfrom the system. The non-volatile memory may also be a random accessmemory.

The non-volatile memory can be a local device coupled directly to therest of the components in the data processing system. A non-volatilememory that is remote from the system, such as a network storage devicecoupled to the data processing system through a network interface suchas a modem or Ethernet interface, can also be used.

In this description, various functions and operations may be describedas being performed by or caused by software code to simplifydescription. However, those skilled in the art will recognize that whatis meant by such expressions is that the functions result from executionof the code/instructions by a processor, such as a microprocessor.Alternatively, or in combination, the functions and operations can beimplemented using special purpose circuitry, with or without softwareinstructions, such as using Application-Specific Integrated Circuit(ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can beimplemented using hardwired circuitry without software instructions, orin combination with software instructions. Thus, the techniques arelimited neither to any specific combination of hardware circuitry andsoftware, nor to any particular source for the instructions executed bythe data processing system.

While some embodiments can be implemented in fully functioning computersand computer systems, various embodiments are capable of beingdistributed as a computing product in a variety of forms and are capableof being applied regardless of the particular type of machine orcomputer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, insoftware. That is, the techniques may be carried out in a computersystem or other data processing system in response to its processor,such as a microprocessor, executing sequences of instructions containedin a memory, such as ROM, volatile RAM, non-volatile memory, cache or aremote storage device.

Routines executed to implement the embodiments may be implemented aspart of an operating system or a specific application, component,program, object, module or sequence of instructions referred to as“computer programs.” The computer programs typically include one or moreinstructions set at various times in various memory and storage devicesin a computer, and that, when read and executed by one or moreprocessors in a computer, cause the computer to perform operationsnecessary to execute elements involving the various aspects.

A machine readable medium can be used to store software and data whichwhen executed by a data processing system causes the system to performvarious methods. The executable software and data may be stored invarious places including for example ROM, volatile RAM, non-volatilememory and/or cache. Portions of this software and/or data may be storedin any one of these storage devices. Further, the data and instructionscan be obtained from centralized servers or peer to peer networks.Different portions of the data and instructions can be obtained fromdifferent centralized servers and/or peer to peer networks at differenttimes and in different communication sessions or in a same communicationsession. The data and instructions can be obtained in entirety prior tothe execution of the applications. Alternatively, portions of the dataand instructions can be obtained dynamically, just in time, when neededfor execution. Thus, it is not required that the data and instructionsbe on a machine readable medium in entirety at a particular instance oftime.

Examples of computer-readable media include but are not limited torecordable and non-recordable type media such as volatile andnon-volatile memory devices, read only memory (ROM), random accessmemory (RAM), flash memory devices, floppy and other removable disks,magnetic disk storage media, optical storage media (e.g., Compact DiskRead-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), amongothers. The computer-readable media may store the instructions.

The instructions may also be embodied in digital and analogcommunication links for electrical, optical, acoustical or other formsof propagated signals, such as carrier waves, infrared signals, digitalsignals, etc. However, propagated signals, such as carrier waves,infrared signals, digital signals, etc. are not tangible machinereadable medium and are not configured to store instructions.

In general, a tangible machine readable medium includes any apparatusthat provides (i.e., stores and/or transmits) information in a formaccessible by a machine (e.g., a computer, network device, personaldigital assistant, manufacturing tool, any device with a set of one ormore processors, etc.).

In various embodiments, hardwired circuitry may be used in combinationwith software instructions to implement the techniques. Thus, thetechniques are neither limited to any specific combination of hardwarecircuitry and software nor to any particular source for the instructionsexecuted by the data processing system.

Although some of the drawings illustrate a number of operations in aparticular order, operations which are not order dependent may bereordered and other operations may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beapparent to those of ordinary skill in the art and so do not present anexhaustive list of alternatives. Moreover, it should be recognized thatthe stages could be implemented in hardware, firmware, software or anycombination thereof.

In the foregoing specification, the disclosure has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope as set forth in the following claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

What is claimed is:
 1. A computer-implemented method, comprising:storing, with a computing apparatus, a plurality of phone numbers;storing, with the computing apparatus, a plurality of funding sources inassociation with each phone number; receiving, in the computingapparatus, a payment request, the payment request identifying an accountidentification number issued by a bank to a user and a transactionamount, the account identification number representing an account of theuser at the bank; determining, using the computing apparatus in responseto receiving the payment request, a phone number associated with theaccount identification number identified in the payment request;determining, using the computing apparatus in response to identifyingthe phone number, a funding source associated with the phone number,wherein the funding source is selected from the funding sources storedin association with the phone number based on at least one of userpreferences and system rules to select the funding source; andprocessing, by the computing apparatus, the transaction amountidentified in the payment request, the payment request using the fundingsource associated with the phone number, the funding source beingdifferent from the account at the bank identified by the accountidentification number, wherein the processing of the transactionincludes transmitting a payment request to a payment server selectedbased on the funding source.
 2. The method of claim 1, wherein thepayment request is received from the bank.
 3. The method of claim 1,further comprising: storing, in the computing apparatus, account data toassociate the phone number with the account identification number;wherein the determining of the phone number is based on the accountdata.
 4. The method of claim 3, wherein the account is one of: a creditaccount, a debit account, a stored value account, a gift card account, aprepaid account, a checking account and a savings account.
 5. The methodof claim 1, further comprising: communicating, by the computingapparatus, with a mobile phone at the phone number to confirm thepayment request.
 6. The method of claim 5, wherein the communicatingcomprises communicating with a mobile phone at the phone number toconfirm the account identification number received in the paymentrequest.
 7. The method of claim 5, wherein the communicating comprisesone of: transmitting a text message to the mobile phone at the phonenumber; receiving a text message from the mobile phone at the phonenumber; communicating with a mobile application running on the mobilephone at the phone number; pushing a notification to the mobile phone atthe phone number; and communicating with the mobile phone via a mobileinterface.
 8. The method of claim 5, further comprising: communicating,by the computing apparatus, with the bank, a payment network, or amerchant acquirer for authorization of a transaction in an amountaccording to the payment request.
 9. The method of claim 8, wherein thecommunicating with the mobile phone is in response to an authorizationapproval of the transaction obtained by communicating with the bank. 10.The method of claim 9, wherein the computing apparatus is configured toobtain the approval without subsequently requesting settlement of thetransaction.
 11. The method of claim 1, wherein the funding source isone of: a credit account, a debit account, a prepaid account, a checkingaccount, a savings account, a payment intermediary account, a storedvalue account, a gift card account, a phone bill, and premium shortmessage service messages.
 12. The method of claim 1, wherein the fundingsource is a stored value account uniquely identified by the phonenumber.
 13. The method of claim 1, further comprising: determining, bythe computing apparatus, a set of one or more premium messages based onan amount of the payment request; and transmitting, from the computingapparatus, the set of one or more premium messages to a mobile phone atthe phone number, wherein a telecommunications carrier is to charge themobile phone according to the set of one or more premium messages. 14.The method of claim 1, wherein the receiving comprises receiving thepayment request from a point of sales (POS) terminal; and the POSterminal is configured to communicate with a mobile device via nearfield communication (NFC) to obtain the account identification number.15. The method of claim 14, wherein the mobile device comprises a mobilephone.
 16. The method of claim 1, wherein the payment request isreceived via one of: internet; mobile application; web browser; personalcomputer; tablet computer; mobile phone; and television.
 17. The methodof claim 1, wherein the receiving comprises receiving the paymentrequest from a payment card reader responsive to the payment card readerreading a payment card carrying the account identification number; andthe payment card that is read by the payment card reader is one of: acredit card, a debit card, a prepaid card, and a banking card.
 18. Atangible non-transitory computer readable medium storing instructionswhich, when executed on a computer, cause the computer to execute amethod comprising: storing, with a computing apparatus, a plurality ofphone numbers; storing, with the computing apparatus, a plurality offunding sources in association with each phone number; receiving, in thecomputing apparatus, a payment request, the payment request identifyingan account identification number issued by a bank to a user and atransaction amount, the account identification number representing anaccount of the user at the bank; determining, using the computingapparatus in response to receiving the payment request, a phone numberassociated with the account identification number identified in thepayment request; determining, using the computing apparatus in responseto identifying the phone number, a funding source associated with thephone number, wherein the funding source is selected from the fundingsources stored in association with the phone number based on at leastone of user preferences and system rules to select the funding source;and processing, by the computing apparatus, the transaction amountidentified in the payment request, the payment request using the fundingsource associated with the phone number, the funding source beingdifferent from the account at the bank identified by the accountidentification number, wherein the processing of the transactionincludes transmitting a payment request to a payment server selectedbased on the funding source.
 19. The method of claim 17, wherein thefunding source is identified by one of: a phone number; an emailaddress; a card number; an account number; and a login for a socialnetworking website.
 20. A system, comprising: a data storage facility tostore account data associating a phone number of a user and an accountidentifier of the user; and an interchange coupled with the data storagefacility, the interchange including a common format processor and aplurality of converters to interface with a plurality of controllers,the converters configured to communicate with the controllers indifferent formats, the converters to communicate with the common formatprocessor in a common format, the common format processor to use oneconverter of the converters to transmit one or more messages to collectfunds via a payment source, the common format processor to store aplurality of phone numbers, store a plurality of funding sources inassociation with each phone number, receive a payment request having theaccount identifier and a transaction amount and use the account data toidentify the phone number based on the account identifier in response tothe payment request in response to the identification of the phonenumber, to identify a funding source associated with the phone number,wherein the funding source is selected from the funding sources storedin association with the phone number based on at least one of userpreferences and system rules to select the funding source, the commonformat processor to process the transaction amount identified in thepayment request, the payment request using the funding source associatedwith the phone number, the funding source being different from theaccount at the bank identified by the account identification number,wherein the processing of the transaction includes transmitting apayment request to a payment server selected based on the fundingsource.